fix(dev): Use correct schema for GHA workflow files in VSCode #4727
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.
VSCode has a feature wherein it auto-detects what schema to use to validate certain JSON and yml files. The problem is, sometimes it's wrong, and when it is, it will throw errors* because it's misconstrued what kind of file you're editing. The incorrect association can be overridden, though, with a correct association in settings.
This PR adds such an association, to prevent VSCode from complaining about our GHA
build
workflow.*It correctly detects that it's a GHA config, but also checks it against the schema for a different build tool called
hammerkit
, and throws errors because the two schemas (schemae?) are incompatible, as can be seen here: