docs(useQuery): Write a story that visually shows useQuery loading/error/success states #73600
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.
There's always been some slight confusion, and lack of clear examples, when it comes to using
isFetching
andisLoading
from react-query. Also we're not super consistent on the names when we create our own loading state variables, which just adds to the confusion...So I made a story that illustrates a few examples where we "load" in data slowly enough to see the state changes happening. Turns out that checking both
isFetching
andisLoading
is probably what we should do all the time.<Suspense>
is also a killer feature to leverage.