Migrating 'Text Area' component
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
**path to the component**
- /src/atoms/TextArea.js
**DoD**
- convert the file to .ts extension
- define an interface for props in the component
- define an interface for internally used states (if any)
- define types for variables (if any)
Contribution steps can be found - [https://github.com/99xt/first-born/wiki/Migrating-to-TypeScript](https://github.com/99xt/first-born/wiki/Migrating-to-TypeScript)
Need support? 😄 add a comment by mentioning one of us.
Contributor guide
Research direction
Open /src/atoms/TextArea.js and read the linked migration guide first. Convert the file to TypeScript, adding interfaces for props and any internal state and types for variables where needed. Done means the component is saved with a .ts extension and all listed typing requirements are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native, typescript
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100