Keep isSuccess consistent when refetching after an error
#4732
+94
−2
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:
isSuccess, such that we don't flip fromfalsetotruetemporarily when refetching after an errorFixes #4240
Investigation
Per #4240, if you have a sequence where:
the observed behavior is:
The issue is that
isSuccesswasfalsewhen the first refetch settled, but then flips totruewhen we start the second refetch. This does seem unintuitive and buggy.Similar to #4731 , I think the logic for calculating
isSuccessisn't sufficient. In this case:Given that, I think the right thing to do is include
&& !lastResult?.isError, leaving us with:I see that flip the second refetch case to stay with
isSuccess: falseas I'd hope.