Skip to content
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

MenubarSub: Each child in a list should have a unique "key" prop. #5976

Closed
Traveller23 opened this issue Feb 15, 2024 · 1 comment · Fixed by #5979
Closed

MenubarSub: Each child in a list should have a unique "key" prop. #5976

Traveller23 opened this issue Feb 15, 2024 · 1 comment · Fixed by #5979
Assignees
Labels
Type: Bug Issue contains a defect related to a specific component.
Milestone

Comments

@Traveller23
Copy link

Describe the bug

This warning appears every time the page is refreshed:
1

Here is the code for my menubar:
2

I don't encounter this warning until I update to version 10.5.1.

Reproducer

No response

PrimeReact version

10.5.1

React version

18.x

Language

TypeScript

Build / Runtime

Next.js

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@Traveller23 Traveller23 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 15, 2024
melloware added a commit to melloware/primereact that referenced this issue Feb 15, 2024
@melloware melloware self-assigned this Feb 15, 2024
@melloware melloware added Type: Bug Issue contains a defect related to a specific component. and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 15, 2024
@melloware melloware added this to the 10.5.2 milestone Feb 15, 2024
@melloware
Copy link
Member

Good catch! Fixed for next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a defect related to a specific component.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants