Slim errors generate poor stacktraces

[grepsedawk]

When I create an error in a slim file (IE calling an undefined method), there is nothing in the trace to point me to which file and where in the file the error originated from.

[joshbuker]

Related to this, I had a weird error from using element.css__class = variable_here # Comment here which took a long time to track down due to the stack trace pointing at a line that didn't even exist in the file. (SyntaxError - syntax error, unexpected keyword_ensure, expecting ')' on line 39 in a file only 37 lines long.)

[stonean]

Some examples of this would be great.

for the line 39 in a file only 37 lines long description @athix mentioned above, the file would be helpful.

[grepsedawk]

Next time I see this I'll grab the whole stack trace.

[stonean]

@pachonk thank you!