-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Each child in a list should have a unique "key" props #5
Comments
yeah, i have noticed it also, the latest releases are not pretty stable, and we are experimenting on upgrading to react; |
there are something wrong with current approach jsx, and I will fix it soon. Previously we have used the jsx production runtime (without warnings) on PROD and DEV builds, so some warnings are expected. But you are right that right now the warnings does not make sense in many cases... |
new release uploaded to clojars |
If you still experimenting some unusual warnings, please reopen this issue. Thanks for the feedback in any case. |
Hi,
Since updating 2022.04.08-137, I start seeing Each child in a list should have a unique "key" props warnings in React dev build, downgrading to 2022.03.31-133 made it go away.
This may not be a rumext issue, rather than a side effect of upgrading to React 18 (or JSX runtime). However, it's bit strange that the warning message even showed up for components that do not use
<li>
elements. Is this expected?thanks for the great library btw!
The text was updated successfully, but these errors were encountered: