Default values

[iainbeeston]

At the moment the test suite doesn't have any tests around default values. I've added a couple of tests (for draft4 and draft3) based on my understanding of how defaults should work.

[zaggino]

I only see this on the default keyword:

http://json-schema.org/latest/json-schema-validation.html#anchor10

Where emphasized word MAY says, that this doesn't belong to the core tests.

[Julian]

Yeah, @iainbeeston, default isn't covered because it doesn't do anything basically. It's just for documentation, there's no validation or action that implementations are required to take.

[iainbeeston]

Interesting. But slightly confusing. I can understand that title and description are for documentation purposes only, but it's less obvious for defaults (not least because defaults are values that may or may not be valid, according to the rfc).

Is there any value in updating these tests to always pass regardless of the default value, to ensure that implementations explicitly do not use defaults during validation?

Right now the Ruby implementation (json-schema) uses defaults during validation if they are defined. The tests in this pull request would pass on that implementation.=

[Julian]

@iainbeeston a test that specifies that defaults can be invalid under the schema would be reasonable sounding to me.

[iainbeeston]

I've added some tests to ensure that an invalid default value does not cause validation to fail.

[iainbeeston]

Sorry, that was badly worded - I've re-written the tests so that they check that bad default values can never make validation fail

[Julian]

Looks great, thanks!