Skip to content

Allow configuration of backtrace exclusion based on wether a line has been matched

Created by: lamont-granquist

If I call a gem or other library and it blows up, then I really want to see those top lines of where the exception got thrown.

This patch preserves the behavior where if I call into (for example) rspec-expectations and it throws in the backtrace I don't want to see that. I also don't want to see any exceptions thrown by gems that rspec gems call to do their work.

Once a single user line (or rspec gem line) is hit, then the behavior reverts to the old behavior and all the bundler/rubygems/rspec/thor spam at the bottom of the exception is still pruned using the same include/exclude tunables.

"Show me if something under my code blew up, do not show me if rspec or something under rspec blew up."

Signed-off-by: Lamont Granquist lamont@scriptkiddie.org

Merge request reports