-
Notifications
You must be signed in to change notification settings - Fork 39
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
fix: create a component tree that matches between client and server to avoid useId
output mismatch
#371
Conversation
TuonoScripts
component
TuonoScripts
componentuseId
output mismatch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few considerations.
Note
Since the PR is still a draft and earlier we hadn't the time to completely discuss the solution some of my comment might be outdated / out of scope 😅.
My main concern at the moment is that resource management will be moved to the router. IMHO we should find a way to keep this kind of logic inside tuono
rather than moving it in tuono-router
.
a174abc
to
1c21680
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made a few changes (listed as separate commits):
The most relevant is the one that moves StrictMode
as first render component on both server and client to be in sync with the react documentation:
Context & Description
Close #369