FIX: Props containing "key" prop is being spread into JSX #4563
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Is this going to be merged? Or is there a workaround? |
|
Hey @kyng-cytro, unfortunately it doesn't look like it as there are other PR's waiting a long time, I recommend checking out patch-package to workaround for yourself, and the best thing is that if/when it does get fixed patch-package will tell you and you simply delete the patch file. |
rsmidt
added a commit
to rsmidt/soccerbuddy
that referenced
this pull request
Dec 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Destructure the key and pass it directly to the Touchable component to resolve error
Related issue
Fixes #4562
Test plan
I struggled to get react-native or expo upgraded to the latest versions in the example folder as it is quite out of date. Please see issue to understand the error thrown by react-native 0.76