eslint-plugin-react
eslint-plugin-react copied to clipboard
jsx-eslint
React-specific linting rules for ESLint
I noticed that there was a schema defining an empty object - it's an unnecessary definition, so remove it.
I noticed that there was a schema defining an empty object - it's an unnecessary definition, so remove it.
We want to ignore a consistent theme of component naming in our project, where the offending component names match a regexp, without having to individually label each of the components,...
As TypeScript is spreading and official ESLint support is given through the [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint) project, I thought it would be convenient if the `.tsx` file extension was supported out of the...
The default RegExp for the boolean-prop-naming rule (`^(is|has)[A-Z]([A-Za-z0-9]?)+`) has an odd syntax that is inefficient and does not test the entire property name. For example, the following propTypes passes with...
This PR aims to fix #1673 by adding a new option to the forbid-prop-types rule: `empty`. This will catch prop types which are functions, such as `shape()` or `arrayOf()`, but...
Pretty naive approach: checking if the call is in an `async` method and if an `await` is found before `setState` (going over tokens). Fixes #1110.
## Overview This PR adds a new rule `no-pure-component-children` which checks that a component extending `React.PureComponent` does not declare `children` as a proptype. ## Motivation Consider standard use of `children`:...
