JSON Schema Validation in VS Code#1564
Merged
ChaelCodes merged 6 commits intorubyevents:mainfrom Mar 31, 2026
Merged
Conversation
marcoroth
reviewed
Mar 25, 2026
03c52b5 to
a0b3c02
Compare
ChaelCodes
commented
Mar 29, 2026
Collaborator
Author
0dfe626 to
4837f55
Compare
This file contains hidden or 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
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.

Description
We can get in-editor schema validation using the yaml-language-server if we store our schemas as json. This allows for autocomplete and validation of our keys without running bin/lint or validate.rake.
This is currently configured for VS Code, but supports multiple editors.
Screenshots
Testing Steps
References