-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Key prop for DOM nodes is actually called 'code' #3669
Comments
That does not make sense, I suspect your copy of React has been modified (probably by search and replace by mistake?). https://github.com/facebook/react/blob/master/src/classic/element/ReactElement.js#L156 |
Yeah, this isn't React – not sure where you got "code". If you search https://fb.me/react-0.13.1.js for "key = config" you'll see that our built copy has |
This was referenced Aug 18, 2021
This was referenced Sep 12, 2021
This was referenced May 13, 2022
This was referenced Nov 27, 2023
This was referenced Mar 22, 2024
This was referenced May 13, 2024
This was referenced May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was trying to fix this warning:
After some searching I ended up in
react.js
, where I found (inReactElement.createElement
):I finally managed to get rid of the warning by using
React.createElement("li", {code: ...})
instead ofReact.createElement("li", {key: ...})
.This should be fixed, probably in
.createElement
, or at least in the docs/warning.The text was updated successfully, but these errors were encountered: