-
Notifications
You must be signed in to change notification settings - Fork 46.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suspense doesn't "resolve" for subsequent times if was suspended again #14013
Comments
I don't think thats intentional, it should handle cases like this without requiring a |
At least it should emit some warning/error, not just quietly show fallback forever. |
This is definitely a bug |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Possibly a bug
What is the current behavior?
Repro demo: GitHub user search.
Type one character and wait after the list is rendered - everything works correctly. Subsequent fetches work this way.
Type two characters faster than results for the first character are rendered and fallback will never go although the second request is successful.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
https://codesandbox.io/s/k5v6ojz107
What is the expected behavior?
Suspense "resolves" with last resolved fetch and renders the list of users
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
react: 16.7.0-alpha.0
react-dom: 16.7.0-alpha.0
react-cache: 2.0.0-alpha.0
The text was updated successfully, but these errors were encountered: