-
-
Notifications
You must be signed in to change notification settings - Fork 580
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: unique key
error
#946
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Thanks for opening this pull request! A maintainer will review it soon.
Pull Request Test Coverage Report for Build 7780067223
💛 - Coveralls |
const vnode = createElement(Fragment, {}, marker, createElement(Effect, { | ||
effect, | ||
deps: hmrTimestamp ? [hmrTimestamp] : [], | ||
}), children); |
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.
is it possible that portals (children) won't have a key and the warning would be shown again?
What I'd suggest is that you spread the children by , ...children
, so this way the whole error would be removed.
}), ...children);
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.
spreading might hit the arguments bound because it has a lower bound than arrays.
Fixes the unintentional unique
key
error thrown by React because ofblock