Async/ await with use client - in documentation - wrong?
Unanswered
Florida White posted this in #help-forum
Florida WhiteOP
Hello everyone. I am working on parallel routes and modal. I found in documentation weird think. In next we cant use async with use client. Right?
10 Replies
@Florida White Hello everyone. I am working on parallel routes and modal. I found in documentation weird think. In next we cant use async with use client. Right?
i hope that this is issue from them copying, because you shouldn't be able to use async component in client context... unless it is weird and allows it
@Florida White Hello everyone. I am working on parallel routes and modal. I found in documentation weird think. In next we cant use async with use client. Right?
The documentation is wrong yes. Thanks for pointing it out, could you please open a PR to fix it?
@Florida White Hi, about your DM, I meant that you open a [pull request](https://github.com/vercel/next.js/pulls) to update the documentation in the https://github.com/vercel/next.js repository. It’s not easy though, if you’re ok with it I’ll do it for you
“Pull request†is usually abbreviated to “PRâ€
Florida WhiteOP
Ah ok ,i will do that.
Florida WhiteOP
It done. Thanks for explanation.
I don’t see your PR here though https://github.com/vercel/next.js/pulls
i see it now: https://github.com/vercel/next.js/pull/57210
but idk if this works (ie i just thought switcher was for jsx and tsx)
Since it exists now I’ll leave the job for the team