fix(types): ensure non-undefined data
on isSuccess with exactOptionalPropertyTypes
#5088
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 #5086
fix(types): ensure non-undefined
data
on isSuccess with exactOptionalPropertyTypesWhen TypeScript
exactOptionalPropertyTypes: true
is enabled,UseQueryStateDefaultResult
could infer
data
asundefined
even onisSuccess
branches. This patch explicitly setsdata: ResultTypeFrom<D>
(andcurrentData: ResultTypeFrom<D>
when!isFetching
)to provide correct type narrowing while keeping
isLoading
asdata: undefined
.data: ResultTypeFrom<D>
data: undefined
only onisLoading
branchcurrentData
required onisSuccess && !isFetching
fulfilledTimeStamp
/error
constraints