You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is clear how to add options and change options which accept arguments, but how do you disable/suppress common project options that don't accept any argument?
For example, given the following .rspec:
--backtrace
What should developers write in their .rspec-local to disable backtracing?
Do you suggest a --no-backtrace option to override a project-level --backtrace just like --no-color/--no-profile do?
You may start here and draw some inspiration here for the start if you would like to tackle adding this option @lackovic. Some changes to docs and tests will come along, but worry not, we'll help you along the way.
.rspec-local
allow individual developers to set options that override the common project options in.rspec
(see Read command line configuration options from files).It is clear how to add options and change options which accept arguments, but how do you disable/suppress common project options that don't accept any argument?
For example, given the following
.rspec
:What should developers write in their
.rspec-local
to disable backtracing?Related issue: #599
The text was updated successfully, but these errors were encountered: