-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Lack of <Suspense>
wrapping an async setup
component should warn
#2603
Comments
You have to use Suspense on the parent (App.vue) of hello world. |
<Suspense>
wrapping an async setup
component should warn
While adding Suspense warnings, for as long that #2215 isn't fixed is it possible to also add a warning when a Currently your async setup component just doesn't show up. Blank screen, no warning on console, no error in JS. |
@posva what about detecting that a Promise was returned, and then await automatically? What's the downside to that? |
It used to warn but was removed (in this commit https://github.com/vuejs/vue-next/pull/2099/files#diff-56930a63772d2e89f19432918b9d6ed851ede4159b0d32404e0c1d8c159fec99L1241) PR #3657 should fix it when merged |
This now seems fixed. In fact the warning appears correctly, the fallback won't appear as it is not at the right place. |
Version
3.0.2
Reproduction link
https://codesandbox.io/s/competent-darwin-lv4zh?file=/src/use/usePropsLoaded.js
Steps to reproduce
Open the codesandbox link and wait 2 seconds.
The usePropsLoaded hook returns a promise which resolves when all props of said component are filled.
Or thats what it tries to do.
Neither #fallback or #default renders at all.
What is expected?
#fallback (at least) to render
What is actually happening?
An warning is thrown on the console:
Unhandled error during execution of scheduler flush. This is likely a Vue internals bug.
The text was updated successfully, but these errors were encountered: