fix: move server component to children of client, not import #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
1 task
|
Closing for now, but feel free to take a look at the changes later. Thank you! |
devjiwonchoi
deleted the
fix/server-component-can-be-children-of-client
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi @UgoRomi! Thank you for opening the issue vercel/next.js#49881 with this wonderful reproduction!
I've just moved around the component structure, and that's it!
This issue is one of the common pattern of misusage of the Client and Server Components.
Please feel free to take a look at this doc as it is well written about this case.
Thank you again, and feel free to ping me if you have anything more!