More descriptive "unable to parse as a literal" error

more descriptive “unable to parse as a literal” error

I made a PR that enhances the errors coming from badly formatted macros (especially with quoting strings which is VERY STRANGE because in some places I have to single-quote, and some places double-quote). Now you don’t need to RESPOND each line of the macro to point which line is faulty, but it shows the exact faulty line, after jinja interpretation.

before:

Unable to parse 'ABS' as a literal: malformed node or string on line 1: 

after:

Unable to parse 'ABS' as a literal: malformed node or string on line 1:  in 'SET_GCODE_VARIABLE MACRO=MATERIAL_PRESET VARIABLE=material VALUE=ABS'

Let me know what you think about that and if you want it to be merged :slight_smile:

Klipper PR

Edit: merged :slight_smile:

1 Like