Skip to content
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

Fix type-specific keywords require a type definition in the schema #8

Closed
bugventure opened this issue Jan 16, 2015 · 0 comments
Closed
Assignees
Labels
Milestone

Comments

@bugventure
Copy link
Owner

According to the JSON-Schema spec:

When the primitive type of the instance cannot be validated by a given keyword, validation for this keyword and instance SHOULD succeed.

An important implication to this statement, is that any conforming validators must validate according to the defined type-specific keyword if the value type matches the type for which the keyword applies. request-validator fails to observe this requirement and does not apply type-specific validator functions, if the schema does not explicitly state the type of the value to validate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant