-
Notifications
You must be signed in to change notification settings - Fork 81
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
Fix unique key warning in collection header #1598
Fix unique key warning in collection header #1598
Conversation
c7ecac3
to
444e4c3
Compare
Can you do exactly like this so no merge conflicts will arise for me in the Signing PR? |
No-Issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks
</DropdownItem> | ||
</div> | ||
<DropdownItem | ||
data-cy='delete-version-dropdown' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the same data-cy value is already used in the first DropdownItem here
EDIT: never mind, they're all different
key |
data-cy |
---|---|
delete-collection-enabled |
delete-collection-dropdown |
delete-collection-disabled |
- |
delete-version-dropdown |
delete-collection-version |
LGTM :)
I am merging this for my PR so I don't have to rebase twice. |
@brumik sorry, I thought I already merged this, thanks 🥲 |
No Issue
A small fix to resolve the unique key warning in the CollectionHeader component, that has been bothering the console log for a while.
