react-component / react-component/cascader
version 2.3.3 file which is Cascader.js set mergedFieldNames's value to INTERNAL_VALUE_FIELD, so that when app run getting warning: '`key` or `value` with TreeNode must be the same or you can remove one of them.'
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 233
- Forks
- 149
- Avg merge
- 10h 23m
- Merged PRs (30d)
- 2
Description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect Cascader.js around mergedFieldNames and INTERNAL_VALUE_FIELD, then reproduce the warning reported for version 2.3.3. Trace how key and value reach TreeNode, and verify that the warning no longer appears while the Cascader continues to work as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100