-
Notifications
You must be signed in to change notification settings - Fork 30.4k
docs: correct use term #89438
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
docs: correct use term #89438
Conversation
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
|
Hiyo, need to add some more fixes: In these two other docs:
We make a link reference to: |
986ec1b to
6c26845
Compare
|
@icyJoseph thanks for the notice. Updated in those and other files as well |
|
@icyJoseph do I need to do something else to push it forward? |
|
@vvscode nope, I take it from here |
docs/01-app/01-getting-started/05-server-and-client-components.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Joseph <sephxd1234@gmail.com>
….mdx Co-authored-by: Joseph <sephxd1234@gmail.com>
|
Nice, you can stop merging canary. I take it from here :) |
### What? `use` is not a hook. It's highlighted in the doc > Unlike React Hooks, use can be called within loops and conditional statements like if. Like React Hooks, the function that calls use must be a Component or Hook. ### Why? It confuses consumers of Next.js and adds field provide misleading proofs ### How? Closes NEXT- Fixes # --> --------- Co-authored-by: Joseph <joseph.chamochumbi@vercel.com> Co-authored-by: Joseph <sephxd1234@gmail.com>
What?
useis not a hook. It's highlighted in the docWhy?
It confuses consumers of Next.js and adds field provide misleading proofs
How?
Closes NEXT-
Fixes #
-->