Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Specify and prototype lossless CSS authoring roundtripping separately

Abierto
  • ¿Algo no está bien?
#460 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
css, rust, typescript
Área
compilers, developer-experience, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
2k
Forks
44
Merge medio
1 d 3 h
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de master-co/css

Todos los issues de master-co/css

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.