theme.json has no styles.elements when no design system is built

Abierto
#5,817 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php, wordpress
Área
backend

Línea de trabajo

Start by reading ThemeJsonProjection::withSystem() and the WordPressSitePlan path that skips it. Trace how the source element styles and unconditional link and heading defaults are projected when no design system exists. Done means those styles appear in generated theme.json, or a diagnostic explains their absence; the issue does not name a test to run.

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

Descripción

Problem

The block-theme scorecard reports link, button and heading as used but unstyled (theme_json fails). The generated theme.json styles has only spacing and typography.lineHeight. Even the unconditional link/heading fontFamily: inherit default in ThemeJsonProjection is missing.

That default is written only inside withSystem(), which is skipped when the site plan has no usage-derived design system (WordPressSitePlan).

Expected

Element defaults, and the element styles observed in the source, are projected even when no design system is built. Otherwise a diagnostic should explain why they're absent.

Seen on

A 36-route import of a site built with a hosted site builder. Its scorecard reports unstyled_used: [link], along with the empty element styles above.

AI assistance: drafted with Claude (Anthropic) via Claude Code from a human-directed import investigation; measurements come from a real import.

Lenguaje dominante
PHP
Estrellas
28
Forks
5
Merge medio
2 h 59 min
PR fusionados (30 d)
942

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 Automattic/blocks-engine

Todos los issues de Automattic/blocks-engine

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.