fix no-key warnings#391
Merged
jacekkolasa merged 1 commit intomasterfrom Oct 27, 2022
Merged
Conversation
AlexNti
reviewed
Oct 26, 2022
|
|
||
| return ( | ||
| <> | ||
| <React.Fragment key={id}> |
Contributor
There was a problem hiding this comment.
I think its safe to complete remove the Fragment here.
Contributor
Author
There was a problem hiding this comment.
@AlexNti There are 2 components inside - Action and ColumnsMenu, perhaps you missed it because of how GH collapses the code?
Contributor
There was a problem hiding this comment.
Oh, yes you correct. I missed that
AlexNti
approved these changes
Oct 26, 2022
burbuli8ra
approved these changes
Oct 26, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
fix 3 no-key warnings when no actions are provided to the table