-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
Anchors naming of 2020 still following 2019 rules #690
Comments
Hey, thanks for reporting. This is actually something that would be a great addition to the Test Suite.
|
Great, let me add in the test-suite let me do it |
@Era-cell I had already gone that route, and it was decided that the Test Suite isn't set up for such tests, and they're just be meta-schema tests. I've already added these locally. There's nothing left to do here. |
@gregsdennis Yeah I read though the issues that day.. Is there a need to set up Test-suite for syntax validation too? or its already done? |
That's a long-standing issue in that repo and should be discussed there with the appropriate people, not in this repo. |
Nuget Package
JsonSchema.Net
Package Version
6.0.4
Operating System
Windows
.Net Target (if relevant, please specify the version in the description)
.Net Framework
A clear and concise description of the bug.
The 2020 spec says anchor naming can start from "_" and not include ":", but _ isnt supported and : still works:
What did you expect?
I expect ":" not to work and "_" to work
Please add test code or steps to reproduce the behavior.
the website where I tested: https://json-everything.net/json-schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"if": {
"properties": {
"foo": {
"$anchor":"it:em",
"const": "then" }
},
"required": ["foo"]
},
"$ref":"#it:em"
}
use 2020 schema evaluation
Is there any other information you'd like to share regarding this bug?
No response
Code of Conduct & Contributor Guidelines
The text was updated successfully, but these errors were encountered: