jsx-eslint/eslint-plugin-react

`react/prop-types`: Option to force TypeScript and propTypes

Open

#3107 opened on Oct 20, 2021

View on GitHub
 (4 comments) (4 reactions) (0 assignees)JavaScript (8,630 stars) (2,797 forks)batch import
enhancementhelp wantedtypescript

Description

Currently react/prop-types will validate prop types regardless of how I define them. I would like to force that both propTypes and TypeScript types are defined.

Contributor guide

Tech stack
javascriptreacttypescript
Domain
frontenddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ESLint rule developmentReactTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Review the existing `react/prop types` rule implementation in `lib/rules/prop types.js`. Check the comments on this issue for any discussions about the desired behavior. Consider adding a new option like `requireBoth` that checks for both TypeScript type annotations and PropTypes. Look at how other options are implemented in the same rule for guidance.