standard/standard

JSX but not React in scope

Open

#351 opened on Dec 2, 2015

View on GitHub
 (46 comments) (0 reactions) (0 assignees)JavaScript (28,844 stars) (2,316 forks)batch import
acceptedenhancementhelp wanted

Description

I'm using JSX syntax to generate virtual-dom/h code using babel plugins (this specifically).

Only problem is, now standard complains because React is not in scope.

Not quite sure how this should be addressed, however. Because that check is useful when using React.

Contributor guide

Tech stack
javascript
Domain
developer experiencetooling
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScript knowledgeESLint rule conceptsAST basicsStandard linter usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the 'react in jsx scope' rule in the standard linter's ESLint configuration. Consider adding a configuration option to disable the React scope check when using custom JSX pragmas. Review comments in #351 for proposed solutions and maintainer feedback on desired approach.