Open
Conversation
✅ Deploy Preview for farfetched ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Problem
When you need create unique cache key you can do it in custom adapter only with duplicated logic on get/set methods. Also useful for params not included in
queryparams: SSR, localization, etc.Solution
Added some kind of optional middleware on key creation step: allow developers modify already created inner key. It can be represented as tag creation based on stores.
Changes description
cachecachewith param usageExample
With localization
Cache posts with localization, using a query call without parameters. After switched locale on new and back you will receive cached data.
SSR + user id
With caution before merge
Badgewith version oncachepage in docs