Add YAML validation contribution point #2122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
VSCode Extension Installation Instructions
|
ellismg
approved these changes
May 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RedHat's YAML extension has a way to specify a contribution point that will map certain file name patterns to a given schema. The comment (e.g. this) at the top of our
azure.yamlfiles does this already, but for user-provided or user-modifiedazure.yamlfiles where that comment is gone, this adds an extra layer of association betweenazure.yamland its schema.microsoft/compose-language-service#122 is vaguely related--mostly in that I'm the one working on that too--but having the Docker extension deconflicted with the YAML extension is in this extension's best interest as well.