-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travel all the errors in report #84
Conversation
d0a5930
to
bf64db8
Compare
@edoput, you mean the second block is the expected output that would be introduced by your change? |
Yes the error reporting was working only on the first layer but the previous change introduces a tour into the second layer But now I have a better one Given the tree structure of the schema we can iterate over every error and subschema recursively and be able to print what is the problem in every definition, this is very verbose so it might not be useful for input with lots of schema errors.
I may have to see if this is a bettter fit for the job but I like where this is going so I call it complete |
Can't wait for it, I also dislike the current situation with validation errors. It's also problematic to represent those errors visually in a UI, but that's another story. |
Ok as the ErrorTree from jsonschema does not recursively explore the errors I call it done. Let's discuss the visual part and then merge if possible We can have a tab As an example here is the directory structure of netjsonconfig printed by
The resulting visual aid should be something like this
Or maybe I can experiment with colors but that may be another PR |
@edoput great! Pay attention to the test coverage which is decreasing, it seems the new lines are not being executed during tests |
f3297cd
to
325b511
Compare
@edoput Great work, thanks for including the tests |
An example is wort thousands words
Raise validation errors