react-component / react-component/input-number
Update tsconfig to enable strict null checks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 323
- Forks
- 188
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 1
Description
There have been multiple issues (#481 , #483 ) caused by the inability to develop the library with strict null checks enabled. These issues do not appear in library development but do appear in client code running with strict checks enabled.
I personally attempted to add strict null check support as part of #482 but was not able to as I don't have the experience necessary with the library to correctly add null checks where necessary.
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 inspecting the repository's TypeScript configuration and the client-facing type-checking path, then review issues #481, #483, and #482 for the failures and attempted approach. Enable strict null checks and update the necessary library null handling so client code compiled with strict checks no longer exposes these issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100