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

Chiusa
  • Qualcosa non va?
#19,669 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
1/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
developer-experience, documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
JavaScript
Stelle
14
Fork
5
Merge medio
4h 16m
PR unite (30g)
688

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/gh-cao

Tutte le issue di githubnext/gh-cao

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.