Skip to content

fix: use applicationId as React key for application cards (#759) - #793

Open
wilsonadenuga wants to merge 1 commit into
Women-Coding-Community:mainfrom
wilsonadenuga:fix/759-duplicate-react-keys
Open

wilsonadenuga wants to merge 1 commit into
Women-Coding-Community:mainfrom
wilsonadenuga:fix/759-duplicate-react-keys

Conversation

@wilsonadenuga

@wilsonadenuga wilsonadenuga commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Description

Application cards were keyed by menteeId, so a mentee with several applications in a cycle
produced duplicate React keys. They now use the unique applicationId, which the API already
returns but MenteeApplicationItem didn't declare.

Related Issue

Closes #759

Change Type

  • Bug Fix
  • New Feature
  • Code Refactor
  • Documentation
  • Test
  • Other

Screenshots

Before — two applications from the same mentee, duplicate key warning:

before-duplicate-key-warning

After — same list, no warning:

after-no-warning

Pull request checklist

Please check if your PR fulfills the following requirements:

@sonarqubecloud

Copy link
Copy Markdown

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.

bug: Admin application lists use key={menteeId}; duplicate keys hide/mis-render cards

1 participant