-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[RFC] createElement changes #14761
Comments
@eps1lon Do we need to keep this issue open? It seems that reactjs/rfcs#107 hasn't made progress. |
I haven't made any progress in investigating if we spread keys. As long as the RFC is open this should stay open as well. |
@eps1lon Ok, this sounds like a great strategy. I will listen to the close event on this React rfcs issue. This made me wonder. Do you think that it would be interesting for Material-UI to have an https://github.com/mui-org/rfcs repository? |
This is a premature tracking issue for changes in reactjs/rfcs#107 that would affect this repository. Don't actually allocate time to this issue. Just something you might want to keep in the back of you head.
defaultProps and function components
react-docgen
Looks doable for static analysis. If anybody encounters other patterns please post them here.
related discussions
key
spreadingUnknown if we do this
refs
As far as I understood this we can get rid of
React.forwardRef
on function components and instead ofdo
which is equivalent to
Really glad about this change. Although it would've been nice if this had landed with the
findDOMNode
deprecation 😩The text was updated successfully, but these errors were encountered: