Skip to content
Browse files

Remove add_setting calls in backtrace_cleaner

this are now unneeded because we've defined instance methods that handle
these configuration options

Signed-off-by: Sam Phippen <>
  • Loading branch information...
1 parent ccf6c25 commit e4a6c2be1414148f66518f059cd51a8f90d0c702 @samphippen samphippen committed
Showing with 0 additions and 13 deletions.
  1. +0 −13 lib/rspec/core/configuration.rb
13 lib/rspec/core/configuration.rb
@@ -80,19 +80,6 @@ def self.add_setting(name, opts={})
- # @macro [attach] add_setting
- # @attribute $1
- # Patterns to match against lines in backtraces presented in failure
- # messages in order to filter them out (default:
- # DEFAULT_BACKTRACE_PATTERNS). You can either replace this list using
- # the setter or modify it using the getter.
- #
- # To override this behavior and display a full backtrace, use
- # `--backtrace` on the command line, in a `.rspec` file, or in the
- # `rspec_options` attribute of RSpec's rake task.
- add_setting :backtrace_exclusion_patterns
- add_setting :backtrace_inclusion_patterns
# Path to use if no path is provided to the `rspec` command (default:
# `"spec"`). Allows you to just type `rspec` instead of `rspec spec` to
# run all the examples in the `spec` directory.

0 comments on commit e4a6c2b

Please sign in to comment.
Something went wrong with that request. Please try again.