Log the full exception trace

[rmckayfleming]

Type of PR (feature, enhancement, bug fix, etc.)

Enhancement

Description

Render the entire stack trace instead of just the top level error.

Why should this be added

Simply put, this makes debugging a lot easier especially for exceptions caused by ViewComponents. I've often run into cases where the exception comes deep from within Rails and without the full trace, it's hard to know what part of your code tripped it.

If it'd be better to gate this behaviour change behind an option or something, I'd be happy to make the change (I'd just need to know how best to handle it).

Checklist

• My code follows the style guidelines of this project
• Checks (StandardRB & Prettier-Standard) are passing
• This is not a documentation update

[leastbad]

Hey Ryan!

I'm curious: would you be happiest if full stack traces occured:

1. only on the server
2. only on the client console
3. both

I'm currently thinking that what makes the most sense is to puts the full trace and keep what the client shows short. What do you think?

[leastbad]

Hey again! 😀

Apologies for moving into your PR like I own the place. Straight talk: you had the right idea, but the implementation needed was closer to a refactoring of the module. I want you to retain credit and be recognized as a contributor to StimulusReflex.

Thanks for kicking things off!

[hopsoft]

This looks good. I had one minor concern.