fix(useQuery): make sure that disabled queries in error state don't throw #2933
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 #2930
one caveat is that the disabled query will be rendered with
status: 'error'
, because that's the state the query is in. Usually, withuseErrorBoundary
, you'd expect to never see a query in error state. However, I think disabled queries can be in all resolved states (success, error, idle), so if you useenabled
, that's what you get. This behaviour is documented with a separate test.