-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
catch missing schemas #46
base: master
Are you sure you want to change the base?
Conversation
something like this
error is ok for me :-) just wanted to do like: https://github.com/geraintluff/tv4#missing-schema |
@adrai normally I would say it's a bug in the schema if a |
Follow up thought: I guess the most important thing is that as a dev I'm not confused about the difference between validation errors and "schema" errors. I know you've created a new property called |
For my use case it does not really matter… it’s just important to know if a schema is missing… Il giorno 24-mar-2015, alle ore 12:34, Thomas Watson Steen <notifications@github.commailto:notifications@github.com> ha scritto: Follow up thought: I guess the most important thing is that as a dev I'm not confused about the difference between validation errors and "schema" errors. I know you've created a new property called validate.missing as opposed to validate.errors, but the question is if that's obvious enough? A throw would just make it really obvious. But again, I might not know your use-case. — |
What's the proposed decision? |
I, too, am eagerly waiting for a decision :-) |
What was/is the decision? |
something like this