Implement $schema

[Julian]

No description provided.

[gazpachoking]

I'm guessing you mean support in the plain validate function, right?

What should happen if a $schema isn't found in the schema, and a validator class isn't explicitly specified? Should we default to one, or error?

[Julian]

Right, in validate.

@validates should be modified to pull the id out of IValidator.META_SCHEMA too.

I think we should default to one. The next release will be 1.0.0 so we can now make that default be draft 4 I think.

[Julian]

Uh. Whoops?

[gazpachoking]

I have something for this, just trying to get all the updates merged in to the draft 4 branch now and tests updated. Do you think we should just have extra keys in validators for the schema uris to look this up?

[gazpachoking]

Okay, here's what I've got. I'm unsure if schema URIs should just be mixed in with the common names in the validators dict like I'm doing right now though.
gazpachoking@112f3d6

[Julian]

Ech yes. I don't know why I said we should get this done before merging, I didn't actually mean that 😦. Let's see here...

[gazpachoking]

Oh, sorry if I was premature there. I was just trying get the updated tests into draft 4 branch before working on it again.

[gazpachoking]

We can always go back and do the merge again if I've done it wrong.

[Julian]

No no :)... It looks fine, I just didn't mean to say "we need this
otherwise we can't merge the other thing".

[gazpachoking]

Oh no, I didn't take it that way. It just felt right to implement $schema in the draft 4 branch, and I wanted to pull in the master changes/tests before they diverged any further.

[Julian]

Ah OK, good. So I'll take a look in a bit, looks more or less mergeable as is.

[Julian]

Merged in #59.