jsx-eslint/eslint-plugin-react

Declaring context type on class component breaks static-property-placement

Open

#3,467 opened on Oct 19, 2022

View on GitHubContributor guide
 (6 comments) (0 reactions) (0 assignees)JavaScript (2,731 forks)batch import
help wanted

Repository metrics

Stars
 (9,293 stars)
PR merge metrics
 (PR metrics pending)

Description

Hi,

After upgrading eslint-plugin-react from 7.31.8 to 7.31.9+ (#2581), it started breaking the declare keyword on context in TypeScript:

Not sure what is the mitigation in this case

Contributor guide

Research direction
Inspect the rule for static property placement to understand how it handles contextType declarations. Compare with previous version to identify the breaking change.
Tech stack
javascripttypescriptreact
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
Node.jsnpmESLint plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70