BetterErrors/better_errors

Can't see errors in templates

manuelmeurer opened this issue ยท 4 comments

With better_errors 2.7.0, when there's an error in one of my templates, this is what I see:

ActionViewTemplateError+at+slack_messages+2020-05-13+16-03-05

Obviously that's not really helpful because I don't see the actual error.

This is the same error with 2.6.0:

NoMethodError+at+slack_messages+2020-05-13+16-00-19

It correctly shows the error in the template.

Thanks @manuelmeurer this is fixed in release 2.7.1 of Better Errors.

(In future, please attach screenshots directly in GitHub instead of linking to an external site. I downloaded and attached the ones you linked to in your PR description.)

Wow thanks for the super quick fix, @RobinDaugherty!

@RobinDaugherty With 2.7.1, I don't see the live shell for ActionView::Template::Error errors:

ActionView:Template:Error at : 2020-05-15 17-09-43

With 2.6.0, it is there:

RuntimeError+at++2020-05-15+16-47-13

For non-ActionView::Template::Error errors, 2.7.1 shows the live shell correctly.
Do you want me to create a new issue for this?

Unfortunately, I noticed this after the new version was live. It's because the backtrace frame containing the context from the template itself is only present in the cause of the exception that was raised. I've opened #466 for this. I've been working on a big change that will allow us to navigate between causes (implementation of #464), which I hope to have out this week.