Proper Exception handling with line number reporting on error about liqp HOT 10 CLOSED

@brettcooper ah yes, I already had some code on my local branch to handle runtime errors for filters which I forgot to commit & push. I just did, and will be in the next release. Thanks.

from liqp.

Yeah, error reporting and source locations where things went wrong are lacking. When I have some more spare time, I'll definitely have a look at this.

from liqp.

I second this. I parse a functioning liquid file and all I get in the error message is
java.lang.RuntimeException: MismatchedTokenException(57!=91)
Any clue how one would begin to debug this?

from liqp.

The numbers refer to ANTLR's token types. MismatchedTokenException(57!=91) means that ANTLR encountered a token with type 57, while the parser expected the token with type 91. These token types are defined inside the generated LiquidLexer.

from liqp.

Are there any plans to introduce this in the near future? Something like strict_variables and some info how to identify which one has failed (to be able to find this in the template)?

from liqp.

Not in the near future. I do welcome PR's, of course :)

from liqp.

If there is someone interested in doing this as a paid engagement, please PM me. We are trying to figure out if we want to do the work or outsource it, as this would help our support team identify issues easier.

from liqp.

Here's a way you could go about providing better error messages: #56

For the time being, I'll leave that PR open for some feedback. Feel free to build upon that branch and submit a PR of your own.

HTH

from liqp.

Any progress or update on this issue? We are also facing the issue of cryptic Liquid error messages that are difficult to understand or troubleshoot. Better exception messaging would be greatly appreciated!

from liqp.

Woohoo @bkiers! Thanks! We look forward to trying the new exception handling.

from liqp.