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

Yacine/fixing nav lists warning and adding other search keys to projects page #1214

Conversation

yacineKahlerras
Copy link

  • fixed "key prop" warning in navigation
  • added more keys to the fuse search in the projects page

@yacineKahlerras yacineKahlerras requested a review from a team as a code owner June 22, 2023 22:24
@changeset-bot
Copy link

changeset-bot bot commented Jun 22, 2023

⚠️ No Changeset found

Latest commit: 738d9bb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@yacineKahlerras yacineKahlerras changed the title Yacine/fixing nav lists warning and adding other search keys to projects page Yacine/fixing nav lists warning and adding other search keys to projects page #1214 Jun 22, 2023
@yacineKahlerras yacineKahlerras changed the title Yacine/fixing nav lists warning and adding other search keys to projects page #1214 Yacine/fixing nav lists warning and adding other search keys to projects page Jun 22, 2023
@Devanshusp Devanshusp linked an issue Jun 30, 2023 that may be closed by this pull request
@@ -46,12 +46,12 @@ const NavDropdown = ({ title, isOpen = false, links }: NavDropdownProps) => {
<Options>
{links.map(({ text, href }, i) => {
return (
<>
<div key={i}>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please don't add a new div, this might change the behavior of the component, do this instead to add key prop:

<React.Fragment key={i}>
....
</React.Fragment>

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good idea thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix "each child needs unique key prop" warning
2 participants