Unknown type not being treated as 'any'

[robbrit]

According to draft 3, if type of a value is not in the list of specified types then any type is valid: http://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.1

Useful for BSON-based databases like MongoDB which have some extra types like ObjectId.

[Julian]

Hey. OK, this sounds reasonable. I read that line in the draft as saying that the validator doesn't have to complain about {"type" : "whatever"} if it doesn't know what "whatever"s are, but I see that the type property defaults to "any", so that makes me see you're right anyhow, since having "type" : "any" should apparently have the same behavior as not having type at all.

That being said I don't think is_type should be changed. This change belongs in validate_type.

[robbrit]

Ah, yeah good call. I will make those tweaks and let you know.

[Julian]

Awesome, thanks.

(And sorry, didn't mean to close, GitHub was being dumb)

[Julian]

Hey. This should be fixed in the linked commit. Thanks.

[robbrit]

Great, thanks! Had been meaning to make the tweaks to validate_type but was having some trouble following the code. Also the project involving the JSON Schema stuff fell on the back-burner for the time being.

[Julian]

No worries. It's a bit hairy, but such is life.
On Dec 30, 2012 12:47 PM, "Rob" notifications@github.com wrote:

Great, thanks! Had been meaning to make the tweaks to validate_type but
was having some trouble following the code. Also the project involving the
JSON Schema stuff fell on the back-burner for the time being.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/47#issuecomment-11766841.