jsx-eslint/eslint-plugin-react

Rule Suggestion: Forbid Classes / Classnames

Open

#1,193 opened on 2017年5月13日

GitHub で見る
 (7 comments) (0 reactions) (0 assignees)JavaScript (8,630 stars) (2,797 forks)batch import
acceptedenhancementhelp wantednew rule

説明

We have a font-awesome <Icon> component that handles accessibility nicely. However, it's still really easy for people to write <i className="fa ...">. It would be nice if we could ban a class based on matching a regex. Obviously, it's tricky/impossible to ban every possible use if people are doing things at runtime, but it would be nice if I could say no to a fair number of cases where this comes up.

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

技術スタック
javascriptreact
領域
toolingfrontend
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
JavaScriptESLintReact
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
35
調査方針
To implement this feature, a contributor should examine existing rules in the `lib/rules/` directory of the eslint plugin react repository to understand the pattern for rule creation. The issue discussion suggests adding a configurable option to match class names via regex, similar to the `no unknown property` rule. The contributor should also review the ESLint documentation on writing custom rules. The issue comments (e.g., from @ljharb) may contain additional requirements or constraints. The new rule should be named something like `no class name regex` and should support an option specifying a regex pattern.
Rule Suggestion: Forbid Classes / Classnames · jsx-eslint/eslint-plugin-react#1193 | Good First Issue