-
Notifications
You must be signed in to change notification settings - Fork 398
Roadmap
This would allow to separate the package cleanly. Formats defined by the draft but which nobody would use anyway could be ousted to a separate project entirely.
Right now, they are poor, to say the least.
Make a structured (JSON based?) validation message class containing all the necessary information.
DONE
Current versions choose to adopt the users' point of view: emails and hostnames should have a domain part. However, there is no requirement at all in the relevant RFCs that either have one. Introduce the ability to restore RFC compliance.
DONE
All features have been implemented, and the user API is stable.
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.
These 4 keywords can potentially spawn other validators from within themselves. The draft is written like this... Try and find a more generic way to spawn validators: array and object validation in general also spawn validators.
This potentially requires a complete change of the internals. Also, there is the difficuly that we want to keep the "keyword validators built by reflection" feature, which is the accelerating feature of this library.