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

Expose effective definition provenance through a public read-only report

Abierto
  • ¿Algo no está bien?
#457 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
css, typescript
Área
api, compilers, documentation, testing

Línea de trabajo

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.

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

Descripción

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/.
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.