jsx-eslint/eslint-plugin-react

feature request: [react/prop-types] recognize generics passed to React.memo

Open

#3866 opened on Dec 12, 2024

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

Description

Is there an existing issue for this?

  • I have searched the existing issues and my issue is unique
  • My issue appears in the command-line and not only in the text editor

Description Overview

eslint v8.57.1 eslint-plugin-react: 7.37.2

Image

Image

Expected Behavior

eslint-plugin-react version

v7.37.2

eslint version

v8.57.1

node version

v18.17.1

Contributor guide

Tech stack
javascriptreact
Domain
frontendtooling
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.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
JavaScriptESLint plugin developmentReact prop types
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue requests that the react/prop types rule recognize generics passed to React.memo. To implement this, examine the rule implementation in `lib/rules/prop types.js` and its tests in `tests/lib/rules/prop types.js`. Look for how React.memo is currently handled and where generics (e.g., `React.memo<Props>`) are not being resolved. Check the existing comments on the issue for any clarification on expected behavior or code examples. The maintainers may need to provide a clear specification of what syntax should be recognized.