-
Notifications
You must be signed in to change notification settings - Fork 56
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
Extract to component bug in generated code #62
Labels
Comments
@KatSick Thanks for your reporting! ill try getting to this in the coming few days, although PRs are super welcome. Id love to point You in the right direction |
@borislit sounds interesting todo... |
@KatSick I found the problem. I hope to have the fix out in coming day or two |
borislit
pushed a commit
that referenced
this issue
Mar 26, 2019
# [4.10.0](v4.9.0...v4.10.0) (2019-03-26) ### Bug Fixes * **class-to-functional:** useState hook not added for state variables not inited or set ([32c71f6](32c71f6)) * **extract-component:** incorrect handling of nested member expressions. Fixes [#62](#62) ([1840c64](1840c64)) ### Features * **extract-component:** added extraction to the same file ([63911e7](63911e7))
🎉 This issue has been resolved in version 4.10.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given input
Extracted generated (Table named) component
As you can see
keyExtractor
is generated incorrectlyThe text was updated successfully, but these errors were encountered: