Standardize prop types
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by reading the linked eslint-plugin-react prop-types rule documentation and inspecting the repository's existing style-guide or lint configuration. Configure the linter to enforce React prop types as required, then verify that the repository's components comply with the rule.
Written by the indexing model from the issue text.
Description
Bring in a linter to standardize react prop types, mark it as required.
https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/prop-types.md
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from leadhomesa/javascript
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
leadhomesa/javascript#1 ·
All issues in leadhomesa/javascript
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cancervariants/metakb#902 ·
-
Two open-case totals on one screen: the Programs tile says 15,858 and the nav badge says 15,868 Openbug frontend maui-pilot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Save States Menu Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100