Fix the load order issues of Sweeping module #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Remove
Concern
from theSweeping
module so we can directly extend it inActionController::Base
WHY
Basically this is what happens, in the context of
ActionController
when the app is booting:Base
loads and includes theCaching
modulerails-observers
railtie is then triggered to includeCaching::Sweeping
concern as a dependency ofCaching
, but it doesn't actually get included becauseCaching
is a concern too.Caching
was already included in step 1, soCaching::Sweeping
never gets included inBase
and people run into this error: Undefined method `cache_sweeper' or uninitialized constant ActionController::Caching::Sweeper #4Note: the tests for this were working before because it didn't use the railtie to load
Sweeping
. It just directly loaded the files withSweeping
in them before it loadedActionController::Base
.FIXES
#4