Remove key
parameter from replace
and use React.cloneElement
instead
#18
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.
Continuation of #16
Issue:
The previous fix to mitigate the React unique keys warning was to pass the
key
as the 2nd parameter in thereplace
method.However, this burdens users with the extra work and responsibility to set the "key" prop on their custom React element.
Enhancement:
The smarter approach done in this pull request was to use React.cloneElement to clone the user's custom React element and merge the key prop for them (when applicable).
Tasks:
key
parameter inreplace
method inREADME.md
.eslintrc