Skip to content

jsonschema should point at what part of the schema causes a SchemaError, similar to SyntaxError #83

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

Closed
Julian opened this issue Mar 10, 2013 · 2 comments
Labels
Enhancement Some new desired functionality

Comments

@Julian
Copy link
Member

Julian commented Mar 10, 2013

This hopefully is a start to alleviate how hard it is to track down errors in large schemas, and shouldn't be too difficult to add.

@Julian
Copy link
Member Author

Julian commented Apr 11, 2013

Implementing this will be a good sanity check to make sure we have all of the structured information on our validation errors that will make this possible to implement.

I think actually that I'm going to take a stab at this tomorrow before going to release.

@Julian
Copy link
Member Author

Julian commented Apr 19, 2013

#90 starts on this.

We can iterate whenever we come up with other good ideas.

@Julian Julian closed this as completed Apr 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Some new desired functionality
Projects
None yet
Development

No branches or pull requests

1 participant