Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Specify and prototype lossless CSS authoring roundtripping separately

Aperta
  • Qualcosa non va?
#460 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
css, rust, typescript
Ambito
compilers, developer-experience, tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
2k
Fork
44
Merge medio
1g 3h
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di master-co/css

Tutte le issue di master-co/css

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.