Avoid rest destructuring React Query result #1925
Merged
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.
The RQ docs are quite clear that you're not supposed to use rest destructuring on results. They even publish a lint rule to catch it. The irony in our case is that we don't even need the destructure — we're putting the object right back together again and doing a totally unnecessary object copy. The only reason we're doing it is to get TypeScript to recognize that
data
must be non-null after we callinvariant
on it. It will do that narrowing on a freestanding variable, but it doesn't like to do it on an object property. So we have to tell it.