Yes, it's my mistake using JSON Schema for something it does not suppose to. Analyzing schema from user input is very difficult if "type" keyword is not required (I actually had read the GH's issue about it). IMHO, JSON is already verbose, no need to make it concise, requiring "type" make it a lot simpler. I'd also prefer not to allow multiple type on "type" keyword.
The fact that the spec is too flexible that allow users to write all nonsensical things, and so sensible things that might have hole on assertions.
I understand all your explanation and thanks for creating a new account to do this, appreciated!
The fact that the spec is too flexible that allow users to write all nonsensical things, and so sensible things that might have hole on assertions.
I understand all your explanation and thanks for creating a new account to do this, appreciated!