Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema Validation Azure DevOps #475

Open
drewkg opened this issue May 18, 2022 · 3 comments
Open

Schema Validation Azure DevOps #475

drewkg opened this issue May 18, 2022 · 3 comments
Labels
Area: VsCodeExtension bug Something isn't working

Comments

@drewkg
Copy link

drewkg commented May 18, 2022

This is just to capture an issue for people searching for the same issue.

The schema validation was not working for a repository that is hosted on Azure DevOps Service. The issue resulted in being the URI of the origin. This particular repository had originally been cloned using the older visualstudio.com URI schema (this did not validate)
e.g.
https://<Organisation>.visualstudio.com/<Project>/_git/<Repo>

Creating a new repo clone using the newer URI schema (this did validate)
e.g.
https://<PAT>@dev.azure.com/<Organisation>/<Project>/_git/<Repo>

@winstliu
Copy link
Member

Interesting, thanks for reporting @drewkg. Can you describe what you mean when you say "schema validation"? Do you mean the new schema auto-detection feature, or something else?

@drewkg
Copy link
Author

drewkg commented May 22, 2022

Apologies, I mean the ability to detect and download the json schema for your instance of Azure DevOps Service which includes the custom plugins that you have installed.

I have only just discovered this VS Code extension so I am unsure if this is new, but it is very useful.

@winstliu
Copy link
Member

Thanks for the report! Both types of URLs should work, so I'll take a look and see what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: VsCodeExtension bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants