naming-convention error for React Functional Components
See original GitHub issueHi! I just upgraded to v8.0.0 and I have problems with @typescript-eslint/naming-convention and React Functional Components.
Say I have something like this:
const MyComponent = (props: Props) => {...}
However that results in:
Variable name MyComponent must match one of the following formats: camelCase, UPPER_CASE @typescript-eslint/naming-convention
Is this a bug or a feature? 😃
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[naming-conventions] React functional component has to be ...
React's naming conventions are to use PascalCase when a function returns a component: //Function name `RoleManager` must match one of the ...
Read more >Specify PascalCase Naming Convetion for Variables of JSX ...
The issue with a rule like this is that it's common and valid to have a helper function that returns JSX that are...
Read more >Error Boundaries - React
A class component becomes an error boundary if it defines either (or both) of the lifecycle methods static getDerivedStateFromError() or componentDidCatch() .
Read more >Handy Naming Conventions for Event Handler Functions ...
When creating a React component which has a prop that handles something, simply follow the onEvent convention (adding a Subject if applicable). Convention...
Read more >React components naming convention ⚛️ | by Charly Poly
In our case, when missing, this means that the component can be present in any product. It's the case of the Sidebar or...
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 FreeTop 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
Top GitHub Comments
🎉 This issue has been resolved in version 8.0.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
Thank you @iamturns !