Improve handling errors by intelligently trimming extremely long lines, when showing the location of the error
richkadel opened this issue · comments
Rich Kadel commented
While fixing an issue revealed by oss-fuzz, the error was related to a generated document that had 1000s of open braces on a single line.
Once the parser was able to catch the error without crashing, it generated an error message that filled my terminal scroll buffer, hiding useful debugging information.
We should be able to trim the line and still show where the syntax error was caught.