Specify and prototype lossless CSS authoring roundtripping separately
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- css, rust, typescript
调研方向
Read site/architecture/styling-ir-roadmap.md and the issue's compatibility constraints first. Define the supported grammar, preservation or refusal policy, versioning boundaries, and measured payload/latency costs before choosing a prototype direction. Done means an RFC with fixtures and parse/print identity tests, snapshot rejection and migration tests, unchanged Manifest codec behavior, and passing boundary and lint checks.
由索引模型根据 Issue 内容生成。
描述
Goal
Decide whether a separately versioned authoring representation can offer lossless CSS source roundtripping, independently of the targeted visual edit preview. Implement a fixture-backed prototype only if the guarantee can be specified without changing Manifest v1.
Roadmap: #456. Design context: site/architecture/styling-ir-roadmap.md.
Concrete use case
A code editor opens an imported stylesheet containing comments, spacing, quoting, duplicate declarations, native functions and mixed Master/native rules, then saves it without an edit. The source must remain byte-identical for the documented supported grammar. Unknown or invalid syntax must have an explicit preservation or refusal policy.
Ownership and compatibility
- Rust parser/compiler owns semantic interpretation; an authoring snapshot, if accepted, has its own version, storage and migration policy. Execution Manifest v1 must not carry CSS text, comments, caches or editor selections.
- Compare a lossless tree against retaining source text plus surgical patches. State supported grammar, error recovery, unsupported constructs, upgrade boundaries and payload/latency budget before promising a public API.
- This is 2.x authoring research, not a 2.0 release gate or implicit commitment to universal CSS roundtripping.
Acceptance criteria
- An RFC records the decision with fixtures and measured costs. If the capability proceeds, parse/print tests prove unchanged-source byte identity across the stated corpus and deterministic refusal for unsupported inputs.
- Separate tests cover authoring snapshot version rejection and migration behavior; execution Manifest codec/hydration behavior remains unchanged.
- No authoring data enters runtime/static output when unused, and compiler/boundary/type/lint checks pass for any prototype.
- 主要语言
- 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
-
难度 1/5 1 小时以内 新手友好度 83/100
-
难度 2/5 1-3 小时 新手友好度 72/100
ranxianglei/billion-context#3583 ·
维护者通常 1 天内回复
-
bug:new
难度 2/5 1-3 小时 新手友好度 76/100
callstackincubator/simlock#673 ·
维护者通常 1 天内回复
-
documentation v3
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
anomalyco/opencode#56380 · 1 条评论 ·
维护者通常 1 天内回复