Closed gonvaled closed 5 years ago
Stepped onto it too.
Sorry for getting around to this so late. I was not maintaining commentjson in between. Got really busy with my day job. I am trying to maintain this now regularly. So expect faster responses.
This is fixed. You can try the latest version of commentjson which addresses this and a lot of other unhandled cases like this.
A quote as the last character in a comment (maybe followed by a space) will crash the parser:
This was difficult to find, specially because the line numbers reported do not make sense (they are line numbers after removing the comments, which does not correlate in the general case with the source file, specially if - like I do - you have lots of blank lines or lines with comments-only)