stylelint-scss VS eslint-plugin-react

Working with SCSS? Check here

Thanks for weighing in, that's good to know. After wondering if this could be auto-refactored, I came across https://github.com/jsx-eslint/eslint-plugin-react/blob/maste..., will definitely have to give that (with `--fix`) a try in the new year and see if I can get the team on board! – desire for typescript being a compelling factor.

Personally I do like the non-destructured `props.abc` throughout component code, really helps clarify at a glance where something is coming from, whether it's locally or externally defined, etc. Code style is an endless exercise in compromises/opinions though, even _with_ tools like eslint and prettier.

eslint-plugin-react react/hook-use-state

The conclusion is to pass callback functions to setState hooks when one needs the current state or props to calculate the next state. React is then able to reliably queue up these "pipes" / transformations to apply to the current state, without relying on what the current state actually is. This is almost so important that there should be an ESLint plugin for this (and there is one).

eslint-plugin-react: React specific linting rules for ESLint.

Here's a great lint rule that can help you catch a lot of instances of untranslated text: https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-no-literals.md

esLint-plugin-react jsx max props per line

I don't know VSCode extension for this, but you can use ESLint and this rule: https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-sort-props.md

Not a VSCode extension, but there is this ESLint plugin that does something similar

eslint-plugin-react [github.com/yannickcr/eslint-plugin-react]

import React, { Component } from 'react';import PropTypes from 'prop-types';class Routers extends Component { static propTypes = { history: PropTypes.object.isRequired };... I tried playing around with the react/prop-types rule, but to no avail.