Expose effective definition provenance through a public read-only report
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- css, typescript
- 领域
- api, compilers, documentation, testing
调研方向
Start with site/architecture/styling-ir-roadmap.md and the related issues #455 and #456 to understand the planned boundaries. Define the versioned public read-only result and documented error or unknown states before choosing the compiler or schema entry point. Done means the public-only example, replacement/import and diagnostic tests, parity and boundary checks, bundle review, and site documentation meet the listed acceptance criteria.
由索引模型根据 Issue 内容生成。
描述
Goal
Expose a read-only, source-located explanation of effective project definitions after imports and whole-definition replacement, without making private parser/binding IR a public SPI.
Roadmap: #455 and #456. Design context: site/architecture/styling-ir-roadmap.md.
Concrete use case
A token browser asks why paint-brand uses a particular utility and token when two imported stylesheets define the same identity. The answer must identify the effective authored definition, its source range, and any replaced definition that matters to the explanation. An unresolved or unavailable source must be reported, not guessed from a default preset.
Ownership and compatibility
- Compiler/project owns import graph orchestration and the public read-only report; Rust owns parser and lowering semantics. Schema may hold a dependency-light contract if consumers require it.
- Keep the report outside runtime bundles and Manifest v1 execution data. Do not expose raw parse IR or
@master/css-internal. - Define a versioned public result and documented error/unknown states before adding an export. Additive 2.x API only; no CSS output change.
Acceptance criteria
- A public-only example explains effective and replaced definitions across imports with stable source identity and ranges, including a missing/unreadable source case.
- Tests cover replacement, duplicate declarations, native conditional blocks, an import/reference cycle diagnostic, native/Wasm parity where applicable, and no silent preset fallback.
- Compiler type-check/build/lint, boundary checks, and runtime bundle review pass. Document the capability and limits in
site/.
- 主要语言
- TypeScript
- 星标
- 2k
- 派生
- 44
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
master-co/css 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 76/100
-
breaking change runtime
难度 5/5 一周以上 新手友好度 35/100
-
runtime server
难度 5/5 一周以上 新手友好度 35/100
-
runtime
难度 5/5 一周以上 新手友好度 35/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
Chocobozzz/PeerTube#7832 ·
维护者通常 3 天内回复
-
Pay to use?未关闭
难度 1/5 1 小时以内 新手友好度 66/100
darkreader/darkreader#16108 · 1 条评论 ·
维护者通常 2 天内回复
-
check:passed streams:add
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
bug engine
难度 2/5 1-3 小时 新手友好度 86/100
frostney/GocciaScript#1746 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
agilepathway/label-checker#739 · 4 条评论 ·
维护者通常 1 天内回复