Invalidating Cache Middleware#381
Merged
Merged
Conversation
matt-gadd
approved these changes
Jun 6, 2019
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.
Type: feature
The following has been addressed in the PR:
prettieras per the readme code style guidelinesDescription:
Built on top of the
cachemiddleware, theicachemiddleware manages lazily value resolution and invalidation.getOrSet: Gets an existing resolved value if it exists in the cache, otherwise sets the value passed.set: Sets the value passed, if the value is a function it will be called and the returned result stored in the cache, or if the result is a promise then it will be added as pending and when the promise is resolved will update the value and invalidate.get: Gets the value for the key or returns undefined if there is no entry or the result is pending.