-
-
Notifications
You must be signed in to change notification settings - Fork 864
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
incorrect warning with option {schemaId: '$id'} and property "id" #521
Labels
Comments
moshewe
changed the title
schemaId flag ignored
Jun 13, 2017
schemaId
flag with an object field named id
moshewe
changed the title
schemaId flag with an object field named id
Jun 13, 2017
schemaId
flag with an object field named id
moshewe
changed the title
schemaId flag with an object field named id
schemaId flag with an object field named id ignores the field
Jun 13, 2017
https://runkit.com/esp/59400ddaca4785001289c821 It should still validate correctly. You can either use it without schemaId option or just ignore the warning |
epoberezkin
changed the title
schemaId flag with an object field named id ignores the field
incorrect warning with option {schemaId: '$id'} and property "id"
Jun 13, 2017
It validates in Runkit and I've also ran it though my tests and you're right, it validates successfully. This warning is misleading, though. |
in 5.1.6 |
Excellent! Thanks a bunch! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the latest version (5.1.5), with the following options:
Compiling this schema:
produces the following message:
schema id ignored { type: 'string' }
I was expecting the object to just be able to have a string property called
id
. I've seen quite a few examples online (e.g. here) for this, so I'm not sure what's wrong here. I suspect it's theschemaId
flag, but I don't understand why it applies to theid
in the property map . I also have no idea how to make the$id
coexist with the property namedid
.The text was updated successfully, but these errors were encountered: