rspec/rspec-core — Issue #490: Don't error out when config.mock_with or expect_with is re-specifying the current config
Author: myronmarston
Created: 2011-10-31 01:23:56+00:00
State: open

See [this comment](https://github.com/rspec/rspec-core/issues/455#issuecomment-2543253). `config.mock_with :rspec` was raising an error for a user due to the 2.7 change discussed [here](https://github.com/rspec/rspec-rails/issues/371). In this case, raising the error was problematic for the user and unnecessary since it `:rspec` is the default and it was essentially a no-op.

We should change the code that raises an error so that it does nothing if these config options are simply re-specifying the current configuration (whether the default or not), since they are essentially a no-op in this case.