Option for "Caused by" backtraces to print more than just the first line

[mpalmer]

Option for "Caused by" backtraces to print more than just the first line

[davidtaylorhq]

This was resolved by #3046, and was released in v3.13.0

[JonRowe]

Thank you for the reminder 😹

[JonRowe]

👋 I'd happily look at PR to improve this, the original behaviour is largely because when it was introduced

Should the default behaviour change at all?

No (with the caveat of I'm on the fence as to whether --backtrace should trigger this new behaviour).

Should the behaviour changes be gated behind new config options, or just use full_backtrace? If the former, should there be one option (say config.cause_backtrace = [:oneline|:regular|:full]) or multiple options (config.cause_backtrace_oneline = true/false, config.full_cause_backtrace = true/false), or something else?

I like the idea of this being a seperate config, what would the three options do? I'm happy for this to be a single "full_cause_backtrace = true/false" or "cause_backtrace = [:oneline|:full]"

Should these options be exposed to the CLI, or is just supporting it in RSpec.configure sufficient for something that is, by the look of it, a very niche feature?

I'd support making the backtrace option take options on the cli e.g. --backtrace=cause is full cause backtrace only, --backtrace=all is max for both, I don't know what to call the current behaviour and I'm on the fence if --backtrace alone should set both to full? Sort of seems like "yes"...