-
Notifications
You must be signed in to change notification settings - Fork 397
Roadmap
Example: in disallow, an unreachable $ref is encountered. This is normally an error, but disallow, as the implementation currently processes it, lets this pass silently.
Right now, the user API is rather messy, with plenty of methods named *Schema(), not all of which actually return a JsonSchema instance.
Find better names, make it easier to get hold of a schema.
There are too many back-and-forths between URIs and JSON References, and issue #20 is proof that JSON Reference support is inconsistent across the code.
Not necessarily in order!
When reporting error messages, right now we only mention the keyword causing the failure. JSON Schema has name and description, but right now these are completely ignored.
Try and insert them?
Android is a platform with many potential uses for such a library. Check compatibility, and see the cost to make the library fully compatible.
Jackson is the library to use for anyone wanting to do JSON in Java, but there are plenty others. Design an interface of some sort so that people can transform their existing JSON data to JsonNode.
Probably required for Android support...
The main problem: exceptions vary. For instance, File's .getCanonicalFile().toURI() throws an IOException, but URL's .toURI() throws a URISyntaxException. All exceptions would need to be wrapped, and it should also be ensured that no unchecked exceptions are thrown.
Also, define "sources". Files and URLs are two obvious candidates. Strings? InputStreams?
Last but not least: how can this integrate nicely and transparently?
Could be nice... That would mean creating a manifest (obviously) and also find a way to create a "complete" jar, ie a jar including all dependencies. TODO: check whether licenses get in the way.
Stop at first validation failure, even non fatal; no messages are collected.
Useful if you are only interested in whether your JSON is valid and don't care about what errors crept in.
The problem: disallow.