-
Notifications
You must be signed in to change notification settings - Fork 114
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
Partial JSON Schema 2020-12 support results in failuer to highlight invalid schema features? #149
Comments
In the meantime, users can install https://marketplace.visualstudio.com/items?itemName=prosser.json-schema-2020-validation, which is powered by https://www.nuget.org/packages/JsonSchema.Net/, which is fully 2020-12 compliant. |
Adding my vote here, VSCode's lack of support for the latest JSON Schema formats is making things harder for my team at the Department of Energy too. |
Also requested in microsoft/vscode#155379 to be picked up by the VS Code team. Currently in backlog |
Vote +1 for fixing this |
+1 upvote to provide a solution for this |
1 similar comment
+1 upvote to provide a solution for this |
+1 upvote to support the latest JSON Schema |
+1 Bump |
@gregsdennis How do you get that extension to override the default validator for JSON files? |
I don't know. I didn't build the extension. My understanding is that it hasn't been maintained for a while either. There are a few outstanding issues in the GitHub repo. |
+1 bump |
+1 |
Imagine the following JSON Schema...
In 2020-12, the tuple form of
items
was replaced withprefixItems
.items
can now only be an object and not an array.However when we look at the in editor validation result...
The value of
prefixItems
is correctly identified as not allowed to be a number. It must be an array.However, the value of
items
is not identified as not allowed to be an array.The VSCode site says
But that doesn't seem to be exactly accurate, especially when a Schema can't be validated as the meta-schema can't be used.
What processing model IS being used when JSON documents identify as using 2020-12?
Don't get me wrong, I'm glad you're working on this!
As always, the JSON Schema team is more than happy to answer questions, and may now even have some time to help fix things if allowed.
The text was updated successfully, but these errors were encountered: