Config set after groups and example are defined may not apply to it
Created by: myronmarston
In #1935, @eugeneius fixed config.include
, config.extend
and config.prepend
so that they apply to existing example groups that have already been defined. In rspec/rspec-rails#1355, we're discussing a similar load-order-based issue and @cupakromer pointed out that config hooks will not apply to groups and examples that are already defined. I think we should address that. More broadly, I think we should audit RSpec::Core::Configuration
and figure out what other config options are similarly subject to load order. define_derived_metadata
is another one that comes to mind; it would be nice to have it apply to the metadata of existing examples and example groups, although mutating metadata after-the-fact has historically had its own set of issues so we'll have to think more about that one.