[fix] Avoid calling getCacheTagsToInvalidateOnUpdate()
twice
#118
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.
I'm using an overridden
getCacheTagsToInvalidateOnUpdate()
to track how many times each tag is invalidated. The wayinvalidateCache()
was originally written calls thegetCacheTagsToInvalidateOnUpdate()
method twice, resulting in the tags being counted twice for each invalidation. This change simply assigns the tags to a variable and uses the variable instead of calling the method directly.FWIW, this is what I'm doing to track the tag invalidations. Just a simple array saved to the cache.