Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Review use of Property name as key

Open
#422 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

Search the Guessers for places where a Property name is used as a React key, then trace the affected rendering path. Reproduce the duplicate-key warning and verify that unnecessary keys are removed or replaced with object IDs, with no repeated keys remaining.

Written by the indexing model from the issue text.

Description

Description
Currently it seems like the Guessers are using the field name as key for some reason?
That causes the console to be rightfully flooded with errors like this:

Warning: Encountered two children with the same key, .$redirectUrl. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

so I'd suggest that's either removed where no key is necessary and replaced with the ID of the object where it is.

Dominant language
TypeScript
Stars
516
Forks
134
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from api-platform/admin

All issues in api-platform/admin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.