-
Notifications
You must be signed in to change notification settings - Fork 57
Roadmap
Ideas thrown in the wild. Not necessarily in order.
Some schemas don't have JSON References. Some schemas can be fully validated before instance validation.
Account for these, simplify pre-validation.
They don't really serve a purpose after all. The JDK has plenty of them already.
Generalize use of msg-simple (DONE)
Using enums is a pain, and not extensible. Allow for extensibility as well (this one should be easy).
Both are in -core for now, but can be used by other packages.
Right now, only schema redirects exist. Also implement path redirects.
Right now, all the logic is "hardcoded" within SchemaLoader
. Split into different processors. Particularly beneficial for URI rework before loading.
Use uri-template now that it is written and functional.
Schema walking is tested, fine; but it is not really put to use.
Also, what about the ability to walk instances? What use would there be?
Some of these may, or may not, make it in 1.2.x.
Not easy to think of "useful" examples for such a generic library...
Right now, this is done by hand. Scenario:
- processor
p1
has outputO1
; - processor
p2
has outputO2
; - processor
p
has an input consisting of a combination ofO1
andO2
.
Find a generic way to allow such combinations. Find a generic way to "wait for" p1
and p2
before invoking p
.
The chain of builders to generate configurations etc is quite long. See if dependency injection can simplify matters somewhat.
Very complicated. And probably not worth it.