Require PascalCase for user-defined JSX components (react/jsx-pascal-case)
See original GitHub issueEnforces coding style that user-defined JSX components are defined and referenced in PascalCase.
https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-pascal-case.md
The following patterns are considered warnings:
<Test_component />
<TEST_COMPONENT />
The following patterns are not considered warnings:
<div />
<TestComponent />
<TestComponent>
<div />
</TestComponent>
<CSSTransitionGroup />
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
SCREAMING_SNAKE_CASE in React Web Development
The message reads: Imported JSX component _Document must be in PascalCase or SCREAMING_SNAKE_CASE eslint(react/jsx-pascal-case) .
Read more >Consider Using `PascalCase` for user-defined JSX components
Consider Using PascalCase for user-defined JSX components JS-0426 ... Imported JSX component textarea must be in PascalCase or SCREAMING_SNAKE_CASE.
Read more >Eslint rule to validate pascal case on react compoent name ...
I'm using Typescript (.tsx extensions), so react/jsx-pascal-case won't work for me. For files that are not components, I do want ...
Read more >eslint-plugin-react - npm
Start using eslint-plugin-react in your project by running `npm i ... react/jsx-pascal-case, Enforce PascalCase for user-defined JSX ...
Read more >step-security/eslint-plugin-react - NPM Package Overview
Start using Socket to analyze @step-security/eslint-plugin-react and its ... react/jsx-pascal-case, Enforce PascalCase for user-defined JSX ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So here underscore(‘_’) in the component name is the culprit for the warning…
Thanks)