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

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

Abierto
  • ¿Algo no está bien?
#19,690 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
12/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
documentation

Línea de trabajo

Read .github/skills/reactive-ui/SKILL.md alongside dashboard/site/src/reactive.js to compare the documented API with the exports and options described in the issue. Done means the skill covers untracked(fn) and the { signal } options for derived, effect, and render; the issue says a branch with changes already exists and provides a pull request creation link.

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.

The reactive-ui skill now matches the current reactive.js API. It documents untracked(fn), which was missing, and the { signal } option on derived. It also states that effect, derived and render all accept an AbortSignal, where it previously mentioned only effects.

No eligible pure-declarative view-source migration was found: the remaining JavaScript-produced sources are simulation-days, the daily-run-count metadata and operational-value-evidence. Moving them would require new or changed production JavaScript, which this task rules out. Skill drift was therefore the fallback task.

No production code or behavior changed.

Evidence

  • untracked and the derived(compute, { signal }) option are exported or defined in dashboard/site/src/reactive.js.
  • render(root, update, { signal }) takes the same signal option.

Validation

  • node --test tests/unit/workflow-contract-selfcare-dashboard.test.mjs passed (15 tests). npm run docs:build was run, but its output was not checked.
  • Dashboard site tests, lint and typecheck were not run. The change is documentation-only and touches no dashboard JavaScript or JSON.
  • No secrets in the diff.
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 · ~51 AIC · ⌖ ~2 AIC · ⊞ 15.7K · ◷

  • expires on Oct 31, 2026, 8:26 PM UTC
Lenguaje dominante
JavaScript
Estrellas
8
Forks
5
Merge medio
2 h 28 min
PR fusionados (30 d)
849

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.