Adding granularity to validation error messages about json-schema-validator

[fge]

Hello,

Well, that is not exactly what I said ;) What I said is that I will probably not be using github's pull mechanism because it lacks a lot of features that I regularly use. You can therefore create a "normal" pull request and I'll merge it... Just not using github ;)

[fge]

Hello,

As you may have seen, the code has changed quite a lot since you have opened this feature request. I have just fetched from your fork but don't see any of your work there.

Given the changes, it may be that you had problems with rebasing or whatever, but in any case, maybe you can just push whatever work you have done "in the past". If you have difficulties rebasing onto the current master branch, I can help with this.

Would you mind giving me an update?

[fge]

Hello,

FWIW: I have added in my roadmap (see https://github.com/fge/json-schema-validator/wiki/Roadmap) the ability to have better error messages. My first idea for this is to internally store the validation error messages as JSON. For instance, for a given path in the instance (we already have that path thanks to ValidationReport's path field) a message could be:

{
    "phase": "instance validation",
    "keyword": "properties",
    "expected": [ "a", "b", "c" ],
    "actual": [ "a" ],
    "message": "required properties missing"
}

The existing .getMessages() method would then be the "serialization" of these as Strings, and you would also have other methods to access all validation messages.

The code is NOT started at all, this is just an idea. Comments?

[fge]

OK well, since then I have implemented quite a lot of it ;) In fact, you cannot add plain strings to a validation report anymore.

Care to review what has been done? This is currently in master (it will not make it in 0.5, changes are too big for that). It is targeted for 0.6.

[fge]

Closing this issue: the work is now done.