Switch to using Statamic's full/half caching#1
Merged
anditopping merged 8 commits intomainfrom Jan 17, 2024
Merged
Conversation
ryanmitchell
changed the title
This file contains hidden or 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
2 participants
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.
One for review - dont merge it until its tested properly.
This would switch us to using Statamic's half cache strategy, which is similar to what our cache was doing. The EntryListener stuff goes into a new
app\Cache\CacheInvalidatorfile and we use our own invalidator to set the logic of when to clear the cache.We just now need to also clear cache when things in the layout are cleared, such as navs. But it shouldnt be a hugely big deal.