Commit 762c163
committed
test(query-core/query): retitle test to reflect actual coverage
The previous title ('fetch should start a new fetch when the previous
retryer has rejected') claimed coverage of the
`this.#retryer?.status() !== 'rejected'` branch in Query.fetch, but that
guard sits behind `state.fetchStatus !== 'idle'`. Once the prior fetch has
rejected and state.status becomes 'error', fetchStatus is already back to
'idle', so the first predicate short-circuits and the retryer.status()
check is never evaluated. Removing the rejected-retryer exception would
not flip this assertion.
Rename and trim to what the test actually exercises: a rejected fetch
followed by a successful refetch via Query.fetch. Per CodeRabbit review
on PR #10529.1 parent dc0cb95 commit 762c163
1 file changed
Lines changed: 1 addition & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
849 | 849 | | |
850 | 850 | | |
851 | 851 | | |
852 | | - | |
| 852 | + | |
853 | 853 | | |
854 | 854 | | |
855 | 855 | | |
| |||
860 | 860 | | |
861 | 861 | | |
862 | 862 | | |
863 | | - | |
864 | 863 | | |
865 | 864 | | |
866 | 865 | | |
867 | 866 | | |
868 | 867 | | |
869 | 868 | | |
870 | 869 | | |
871 | | - | |
872 | | - | |
873 | | - | |
874 | | - | |
875 | | - | |
876 | 870 | | |
877 | 871 | | |
878 | 872 | | |
| |||
0 commit comments