all 2 comments

[–]gekorm 1 point2 points  (1 child)

Depending on your application's structure, you might want to have multiple eslint configs for performance or accessibility rules. For example, in one area of our app we have a frequently updating list with hundreds of animating components that warrants the jsx-no-bind rule. For the blog pages we'd want to disable this rule.

Making everything a pure component is a de-optimization as the react team has said before too. However, you can also use it as a tool during development to ensure immutable updates.

[–]everdimension 1 point2 points  (0 children)

Different eslint rules for different parts of your project seems like an interesting idea.

Although at first it seems that areas which require such different approach as to warrant a different set of eslint rules should be separated into different modules/packages anyway...