Syntax error halts validation of other files and prints backtrace about check-jsonschema HOT 8 CLOSED

Sorry, did I say the next couple of hours? I meant minutes! 😅
(The fix and testing for it came together surprisingly easily.)

v0.18.2 is now available with the fix. Please give it a go and let me know if it still isn't working for any reason!

from check-jsonschema.

Works perfectly fine! Thanks so much for the quick replies, this is the most usable tool of all yaml/json linters/checkers for use in a git hook.

from check-jsonschema.

That sounds like a reasonable use-case and a good improvement to the behavior! Consider this "accepted" -- I'll try to find time to work on this.

from check-jsonschema.

I've just released v0.18.0, which changes the way that parsing errors are handled to accommodate this.
The error output has changed slightly, and it should no longer stop processing when a file fails to parse.

I hope this works well for you. Let me know if you run into issues with it!

from check-jsonschema.

Thank you so much! It works very well for JSON, but invalid YAML files still crash the tool, unfortunately. They crash with a ScannerError, which seems like is not being caught in the code yet.

from check-jsonschema.

Can you provide me with a sample YAML file which crashes things in this way? I tested against YAML and other formats, so it's supposed to work, but I guess I'm missing some case(s).

from check-jsonschema.

For example:

foo: bar
invalid

from check-jsonschema.

Thanks for the example! I'm able to reproduce and I see the cause.

The current code catches ruamel.yaml.ParserError, but that only refers to errors during the parse phase of YAML loading. The above produces a ScannerError (IIRC "scanning" is tokenization/lexing).
I should probably broaden the error class to the base YAMLError. I expect to have a fix done, tested, and released within the next couple of hours.

from check-jsonschema.