The output on the HTML error response could point to the exact component .rb file as an improvement (similar to how it shows the helper exact line in the screenshot), but just mimicking what Rails does in console for ERB would help immensely. The stack trace I wanted was behind the "Framework Trace" button but I assumed it was truncated from the main stack trace due to how big it was.
If I get an error in a template, the stacktrace can get very noisy. From optify, with an error on the imgix-rails gem:
With a default ERB file:
Also, if the error is in a helper (close to what a component is in Rails world), this is what I get:
error_in_helper
is the name of the method I defined.And this is what the browser show:
Ideally, the stack trace should look something like this:
The output on the HTML error response could point to the exact component
.rb
file as an improvement (similar to how it shows the helper exact line in the screenshot), but just mimicking what Rails does in console for ERB would help immensely. The stack trace I wanted was behind the "Framework Trace" button but I assumed it was truncated from the main stack trace due to how big it was.