[self-care:reactive-ui] Align reactive-ui skill with element registration and view metadata

Aperta
  • Qualcosa non va?
#20,042 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
20/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, markdown
Ambito
documentation

Direzione di ricerca

Read .github/skills/reactive-ui/SKILL.md and the spec in dashboard/site/src/specification.js (VIEW_KEYS, VIEW_ELEMENT_VALUES) and dashboard/site/src/components/ui-elements.js (LAZY_ELEMENT_RENDERERS). Update SKILL.md to describe element registration and lazy rendering as specified. Done when skill text matches the current implementation and docs/dashboard-language-specification.md.

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.

This updates the reactive-ui skill so its guidance for named UI elements matches the current implementation. No production code, dashboard document, or test changes.

No eligible pure-declarative view-source migration exists. The remaining JavaScript-produced source is the synthetic simulation-days source. It is also consumed by the validator and by declarative.js, so migrating it would need production JavaScript changes.

Fixes
  • The skill said to "record a concise intent" on elements. VIEW_KEYS has no intent; it belongs to pages and row actions. The skill now says to register the element name in VIEW_ELEMENT_VALUES and to give the view subject, objective, and acceptance, with sources in data.sources.
  • The skill's lazy-registration note was vague. It now names the actual mechanism: a <name>-lazy entry in LAZY_ELEMENT_RENDERERS via lazyElementRenderer.
Evidence
  • dashboard/site/src/specification.js: VIEW_KEYS, VIEW_ELEMENT_VALUES
  • dashboard/site/src/components/ui-elements.js: LAZY_ELEMENT_RENDERERS, lazyElementRenderer
  • docs/dashboard-language-specification.md: DLS-VIEW-002 and DLS-VIEW-022
Validation

Documentation-only change to a skill file, so no test suites were run.

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 · ~59 AIC · ⌖ ~2 AIC · ⊞ 16K · ◷

  • expires on Nov 7, 2026, 7:37 PM UTC
Lingua principale
JavaScript
Stelle
14
Fork
5
Merge medio
3h 29m
PR unite (30g)
761

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.