-
Notifications
You must be signed in to change notification settings - Fork 233
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
Consider Shipping Newer JSONSchema Version #704
Comments
This extension inherits JSON schema support from vscode-json-language-service. I think it is best to follow up on this issue or similar ones for this support. |
Thank you for the swift reply! My apologies I was unsure if it was an upstream issue or not so thank you for the clarification. |
The unevaluatedProperties seems to work in JSON schema but not in yaml schema... |
that issue has been fixed but this extension still does not seem to support |
@gorkem The upstream issue is resolved a while ago. But it still doesn't work for this plugin. Are there any plans to resolve this? |
@gorkem When will this be resolved? |
Unfortunately, I am not actively working on it. |
Support in vscode-yaml for JSON Schema draft 2020-12 would make a huge difference for us. We use JSON Schema to build out frontend forms and backend validation and use also YAML as an input format edited in VSCode. Amongst the draft 2020-12 features we would like YAML validation support for is Latest draft support may also address the annoying 'problem' message: To confirm, the VSCode native JSON support does provide inline validation of 2020-12 keywords. Our teams love this extension and as far as I know no other extension provides these excellent features. |
Hi, |
As the README says:
I would love to use features from a newer draft (specifically I'm looking at
unevaluatedProperties
though a lot of it is good). So shipping with the ability to use 2020-12 would be great! I tried looking around to see if there's any way to configure it to ship with a newer version or a reason why it would be, say, backwards incompatible and thus not implemented.I tried searching the issues with the keyword
jsonschema
etc. so I hope this isn't a duplicate issue or answered somewhere obvious!The text was updated successfully, but these errors were encountered: