You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The synthesized frame doesn't have a binding, so there's no live shell for it. There is a binding that could be used for this frame, but it's in the cause's top stack frame, not deeper in the most recent (topmost) error's stack frame.
One solution is to show the cause of the ActionView::Template::Error instead of synthesizing a backtrace frame. That would be a quick fix, but has the disadvantage that there might be useful debug information in the topmost error.
#464 would solve this while allowing the developer to navigate between the causes instead of only showing a specific one. A nice-to-have in that case would be for Better Errors to show the second cause in the chain by default, while still allowing navigation back to the ActionView::Template::Error.
The text was updated successfully, but these errors were encountered:
The synthesized frame doesn't have a binding, so there's no live shell for it. There is a binding that could be used for this frame, but it's in the
cause
's top stack frame, not deeper in the most recent (topmost) error's stack frame.One solution is to show the
cause
of theActionView::Template::Error
instead of synthesizing a backtrace frame. That would be a quick fix, but has the disadvantage that there might be useful debug information in the topmost error.#464 would solve this while allowing the developer to navigate between the causes instead of only showing a specific one. A nice-to-have in that case would be for Better Errors to show the second cause in the chain by default, while still allowing navigation back to the
ActionView::Template::Error
.The text was updated successfully, but these errors were encountered: