Rule idea: no-mutation-props · jsx-eslint/eslint-plugin-react#1113

(6 comments) (8 reactions) (0 assignees)JavaScript (8,630 stars) (2,797 forks)batch import

help wantednew rulequestion

説明

A component is never meant to modify its own props (https://facebook.github.io/react/docs/components-and-props.html#props-are-read-only).

I suggest we had a no-mutation-props rule to check for mutations of a components own props. It looks like we could likely copy the logic used in no-direct-mutation-state.js.

コントリビューターガイド

技術スタック: javascriptreactnodejs
領域: toolingdeveloper experience
Issue 種別: feature
難度: 3
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: ESLint plugin developmentReact props immutabilityAST manipulation
初心者向け度: 65
調査方針: Look at the existing rule no direct mutation state.js in the same repository (lib/rules/no direct mutation state.js) to understand the logic for detecting mutations. Adapt it to detect mutations of props instead of state. Consider edge cases like nested props and object spread. Review the React documentation link provided in the issue. Check the issue comments for any additional discussion on implementation details or scope.