-
-
Notifications
You must be signed in to change notification settings - Fork 574
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
'required' in 1.0.0 no longer works as in 0.8.0 #73
Comments
Hi. This is because your So the behavior there is because it's falling back to Draft 4 since it doesn't know about that Whether or not without the fragment should also be recognized as draft 3 I think revolves around another discussion that has been going on about relative URIs vs JSON References, so I'm not sure: @fge @gazpachoking should http://json-schema.org/draft-03/schema and http://json-schema.org/draft-03/schema# both be accepted for draft 3 schemas? |
Yes, since the first is the URI of the document itself, and the second is the empty pointer into that document -- ie, for all practical purposes, the document itself. |
OK, sounds good. Thanks for confirming. I guess to properly implement |
On Fri, Mar 1, 2013 at 8:22 PM, Chase Sterling notifications@github.com wrote:
Hold on, "$schema" is not "$ref". You don't need to resolve it. But if And when normalizing a URI, whatever it is, the fragment is always Francis Galiegue, fgaliegue@gmail.com |
On Fri, Mar 1, 2013 at 8:28 PM, Francis Galiegue fgaliegue@gmail.com wrote:
FWIW, this is why I have a Francis Galiegue, fgaliegue@gmail.com |
Yeah, that answers it. I just thought that after normalization there would be one way to refer to the same schema, rather than the # still being optional. |
Fixed in #77 |
Thanks for reporting this @ptallada . There will be either a bugfix release or a minor release tomorrow so this should hit you soon if you're not on HEAD. Cheers. |
Wow, what a fast response :D Thank you very much! |
Hi,
In 0.8.0, the None value would validate with the following schema:
{
"type" : "null",
"$schema" : "http://json-schema.org/draft-03/schema",
"required" : true
}
Now, with the same schema, in 1.0.0 it fails with the following error:
SchemaError(u"True is not of type u'array'", u'type', deque([u'required']))
The text was updated successfully, but these errors were encountered: