-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Create JSON schema for config #149
Comments
Welcome collaborator, as usual :) |
Here is a PR to SchemaStore. |
Doesn't SchemaStore have some way of handling versions? Imagine anytime any of these schemas are updated on the master branch, it will prevent all users of an older version from using it, and in some cases - when the master contains an unreleased code - it will prevent everybody from using it. |
It does. ;) There are two ways to implement multiple version support: via catalog.json from SchemaStore or directly inside schema via When there are multiple versions presented via |
So what will be the course of action when one of these schemas you made needs a new version? |
Just create a new JSON schema with some edits incorporating new features. ;) In VS Code in such situation, editor notifies that multiple schemas match some file and lets to chose what file version is used. |
You can assign me to this task as always. ;)
The text was updated successfully, but these errors were encountered: