Wire @shadcn/lint into the consumer lint pipeline (template ships the dep and DESIGN.md claims enforcement, nothing runs it)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- eslint, typescript
- 领域
- tooling
调研方向
Read the child template's lint script and devDependencies, its DESIGN.md, and the @shadcn/lint implementation of shadcn/no-restyle. Compare the current Biome-only pipeline with the three proposed approaches, then decide how the framework should keep enforcement and documentation aligned. Done means the chosen approach is implemented consistently for generated children and the DESIGN.md claim matches what the lint pipeline runs.
由索引模型根据 Issue 内容生成。
描述
What happened
The child template ships @shadcn/lint in devDependencies, and the child's DESIGN.md states: "@shadcn/lint's no-restyle enforces this" for design-system usage. Nothing runs it: the only lint script is biome check .. The design-system rule the docs present as enforced is a documentation claim.
Why the gap
@shadcn/lint is a programmable agent-first linting plugin — an ESLint augmentation (shadcn/no-restyle), with no bin. Consumers whose pipeline is Biome-only never execute it.
Options
- Ship an optional ESLint pass in the consumer lint pipeline that computes
shadcn/no-restyleoverui/src(and document it in DESIGN.md accordingly). - Port
no-restyle's mechanical checks into the Biome config (if feasible) — keeping a single linter. - Soften the docs: DESIGN.md states the rule as review-time convention in CODING_STANDARDS.md instead of claiming tool enforcement.
Decide in the framework so docs and enforcement never diverge per-child again.
Reference: citynode.app ui/DESIGN.md vs pnpm run lint (biome only).
- 主要语言
- TypeScript
- 星标
- 5
- 派生
- 3
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 152
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NEARBuilders/everything-dev 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
NEARBuilders/everything-dev#628 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
NEARBuilders/everything-dev#400 ·
维护者通常 1 天内回复
-
Onboarding at events: translate /onboard, use "community" wording, and handle failed invite lookups未关闭
难度 4/5 3-5 天 新手友好度 42/100
NEARBuilders/everything-dev#653 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
NEARBuilders/everything-dev#652 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
NEARBuilders/everything-dev#651 ·
维护者通常 1 天内回复
查看 NEARBuilders/everything-dev 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
liberation-data/drivine#428 · 1 条评论 ·
维护者通常 1 天内回复
-
GitLab: a merge request closed without merging keeps the Git toolbar on View MR instead of Create MR未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
code-yeongyu/oh-my-openagent#11731 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100