fix: re-render when returned data and fallbackData is the same and keepPreviousData is enabled #2169
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.
Fixes #2128
This fixes an issue that happens when
keepPreviousData
is enabled and the returned data and the fallback data is the same.In this case, we have to check the laggy data, not only the fallback data, to update returned data from laggy data to the latest data. Currently, an update is ignored if the latest data and the fallback are the same.