react-component / react-component/checkbox
about useMergedState(null,{...})
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 132
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
/** We only think `undefined` is empty */
function hasValue(value: any) {
return value !== undefined;
}
I think using useMergedState is unreasonable
<Checkbox checked={null} defaultChecked={true} onChange={onChange}>
Checkbox
</Checkbox>
{/* Correct */}
<input type="checkbox" checked={null} defaultChecked />
Show different results
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
Start by tracing the Checkbox useMergedState path and compare its handling of checked={null} and defaultChecked with the native input example in the issue. Done should mean the Checkbox and native input produce the intended matching results, with the relevant behavior covered by an appropriate test.
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