feat(query): staleTime of Infinity always fresh. #98
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
✅ Deploy Preview for funny-banoffee-0afb46 canceled.
|
nakagam3
changed the title
|
Thank you for your kindness! Your approach was really nice. |
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 PR modifies the
staleTimeoption to acceptInfinityas a valid value. IfInfinityis specified, the cache will remain fresh indefinitely after the initial fetch, unless manually refetched.This is useful in cases where the data doesn't update frequently, so refetching is unnecessary, and we may want to disable it for performance reasons.
I welcome your feedback on this change and am happy to make any necessary adjustments.