No React/Vue satisfiedBy guidance for the 58 frontend laws
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 56/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- react, typescript
调研方向
Start by locating the 58 frontend laws and reading the detector for one law you know from React or Vue; the issue does not name specific files. Write guidance only for behavior the detector actually accepts, and verify it against a real project. Done means the entry accurately explains how to satisfy the check, or records that the concern has no equivalent in detectionLimits.
由索引模型根据 Issue 内容生成。
描述
The 58 laws with stack: "frontend" run on any frontend project — Angular, React, Vue,
Ionic. Their satisfiedBy guidance is written only for Angular (satisfiedBy.angular,
67 laws). A React or Vue team is told the law applies to them and then handed OnPush,
standalone components and NgRx.
This is a gap in what we have authored, not a bug in the data. See #11 for why renaming
the key would be the wrong fix.
What "done" looks like
For each frontend law, a satisfiedBy.react / satisfiedBy.vue entry written the way
the Angular ones were: after reading the detector, describing what actually makes the
check pass in that framework. Not a paraphrase of the Angular text with the nouns
swapped.
Two things to hold to:
- Never invent. A plausible-sounding instruction that does not actually satisfy the
detector is worse than an absent one — it sends people to change code for nothing. - Where a law's concern has no React/Vue equivalent, say so explicitly rather than
inventing an analogue. Some of these 58 will legitimately have nothing to say outside
Angular, and that belongs indetectionLimits.
Good first contribution for someone who works in React or Vue daily: pick one law, read
its detector, write the entry, prove it against a real project.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 38 分钟
- 30 天内合并 PR
- 96
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
Rule-Of-Code/RoC 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
Rule-Of-Code/RoC#436 ·
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 35/100
Rule-Of-Code/RoC#439 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 49/100
Rule-Of-Code/RoC#438 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 53/100
Rule-Of-Code/RoC#437 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 74/100
Rule-Of-Code/RoC#435 ·
维护者通常 1 天内回复
相似的 Issue
-
ready-for-agent
难度 1/5 1 小时以内 新手友好度 86/100
LucasSantana-Dev/Lucky#3257 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
danielmiessler/LifeOS#2894 ·
维护者通常 5 天内回复
-
enhancement frontend good first issue help wanted testing-infrastructure
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 2 天内回复
-
enhancement follow-up
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复