Nested schema objects raise "schema missing"

[chaijs]

Nested schema objects raise "schema missing"

[thabemmz]

Hi @baylee,

This is caused by using the id property in your definitions and is, generally speaking, only useful when you're working with loading schemas from a URL. See http://json-schema.org/latest/json-schema-core.html#anchor27 for more information.

About your example, as defined in the definition of JSON Schema:

The "id" keyword (or "id", for short) is used to alter the resolution scope. When an id is encountered, an implementation MUST resolve this id against the most immediate parent scope. The resolved URI will be the new resolution scope for this subschema and all its children, until another id is encountered.

This means all nested properties within #/definitions/questions that use a $ref property are resolved as questions#/definitions/answers (questions being a schema identifier here). Since the questions schema isn't defined explicitly, this always errors.

The solution here is to remove the id property from your definitions as you probably don't need it. With the id fields removed this schema validates properly.

For more information about handling id fields, see tv4 (we're using this internally for validation).