jsx-eslint/eslint-plugin-react

Rule Suggestion: Forbid Classes / Classnames

Open

#1,193 创建于 2017年5月13日

在 GitHub 查看
 (7 评论) (0 反应) (0 负责人)JavaScript (8,630 star) (2,797 fork)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
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
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.