Addresses #13 by outputting the snippet file name and offending line number when a snippet fails to parse.
Before this change:
After this change:
Despite the error message/code being different in the above logs, the root cause was a trailing comma in all cases. I wasn't able to find a way to interpret that, so I simply added a catchall tip for the user to check for trailing commas.
Addresses #13 by outputting the snippet file name and offending line number when a snippet fails to parse.
Before this change:
After this change:
Despite the error message/code being different in the above logs, the root cause was a trailing comma in all cases. I wasn't able to find a way to interpret that, so I simply added a catchall tip for the user to check for trailing commas.