Abstract out provisioning across all component types #340
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes #332.
This PR will introduce a new behaviour and service based on provisioning. Instead of it being part of hooks, as before, it's now a separate
Cachex.Provisionmodule which can be used in any component to accept provisions. Most notable this is now also supported in warmers, so they can have an up to date version of the cache structure.This PR will also name the cache warmers after their module. This is temporary, because eventually they'll be named (via #334) - but naming was required to implement this properly. It was only not done in the past due to not being tied to a major release.