[self-care:reactive-ui] Sync reactive-ui skill with reactive.js API

Cerrado
  • ¿Algo no está bien?
#19,669 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
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
developer-experience, documentation

Línea de trabajo

The proposed documentation update concerns .github/skills/reactive-ui/SKILL.md and the API in dashboard/site/src/reactive.js. Read those files and compare the documented derived and untracked APIs; the issue says npm run docs:build passed. However, the issue body contains a ready-to-create pull request link and says the changes are already pushed, so the work appears to be underway.

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

Descripción

agentic-workflows self-care self-care:reactive-ui-expert

[!TIP]
Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.

Documentation-only fix: the reactive-ui skill now matches dashboard/site/src/reactive.js. No dashboard behavior changes.

  • derived(compute, { signal }) accepts an AbortSignal (the skill omitted it).
  • untracked(fn) is exported and used by components but was undocumented.

Selection: No eligible pure-JSON view-source migration exists. The remaining JavaScript sources are simulation-days (a synthetic 30-day sequence that Dashboard Language cannot generate) and operational-value-evidence (a validated packet-to-fact flattening). Neither can be replaced without new production JavaScript. This is therefore a skill-drift fallback.

Evidence: dashboard/site/src/reactive.js (derived, untracked).

Validation: npm run docs:build passed. Docs-only change, so typecheck, lint and e2e were not applicable.

Control Plane

[!NOTE]
Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by SelfCare / Reactive UI Expert · copilot · auto · ~44 AIC · ⌖ ~1 AIC · ⊞ 15.7K · ◷

  • expires on Oct 31, 2026, 1:51 AM UTC
Lenguaje dominante
JavaScript
Estrellas
14
Forks
5
Merge medio
4 h 16 min
PR fusionados (30 d)
688

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 githubnext/gh-cao

Todos los issues de githubnext/gh-cao

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.