React
Best practice
react-legacy-component
react-legacy-component
Legacy component lifecycle was detected - $METHOD.
react-props-in-state
react-props-in-state
Copying a prop into state in React — this is bad practice as all updates to it are ignored. Instead, read props directly in your component and avoid copying props into state.
react-props-spreading
react-props-spreading
It’s best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious actors a way to inject unexpected attributes.
react-find-dom
react-find-dom
findDOMNode is an escape hatch used to access the underlying DOM node. In most cases, use of this escape hatch is discouraged because it pierces the component abstraction.
define-styled-components-on-module-level
define-styled-components-on-module-level
By declaring a styled component inside the render method of a react component, you are dynamically creating a new component on every render. This means that React will have to discard and re-calculate that part of the DOM subtree on each subsequent render, instead of just calculating the difference of what changed between them. This leads to performance bottlenecks and unpredictable behavior.