react-component / react-component/input-number
Pass onChange Native Event Back
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 323
- Forks
- 188
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 1
Description
Instead of passing back just the number with the onChange event it would be a more consistent experience to get back the actual event from the input back to the consumer of this component.
Doing so will make it easier and more consistent to process events that come back from other input type elements.
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 at the component's onChange entry point and trace how the input event is currently converted before reaching consumers. Check the existing tests around onChange behavior, then confirm that consumers receive the native event while preserving the component's current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100