Expose attribute documentation and metadata during diagram inspection

Aperta
#28 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript

Direzione di ricerca

Start by tracing how attribute nodes are rendered and how diagram selection connects to the Inspector; the issue does not name specific files or tests. Inspect the linked model examples at the reported revision to identify authored documentation and supported metadata, then check how the editor preserves source provenance. Done means keyboard accessible inspection of both raw documentation and standardized metadata, with long text handled at narrow widths; current behavior still needs reproduction.

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

Descrizione

enhancement

Source and status

WP26 feedback report — Suggestion 3; section 2 item 9. Session dated 2026-11-10, using the hosted editor as served that day; deployed commit was not identified. The report does not establish current develop or current deployment behavior.

Reported by Zargham in WP26; not independently reproduced by maintainers.

Problem

The model records effectiveness/performance classifications in attribute documentation, but readers cannot see those descriptions or metadata in diagrams.

Reproduction / requested workflow

  1. Open an attribute node with doc text or supported metadata annotations.
  2. Try pointer, keyboard selection and Inspector to discover its meaning.

Acceptance / investigation criteria

  • Provide accessible inspection of supported authored documentation/metadata, via Inspector or tooltip/detail affordance.
  • Preserve exact source provenance and distinguish raw doc text from standardized metadata.
  • Handle long text and keyboard access at narrow widths.

Evidence

Model files at the reported revision.

Preserve unapplied drafts and the last valid model. Record exact engine/build identity and distinguish a reported observation from a newly reproduced result.

Lingua principale
TypeScript
Stelle
2
Fork
0
Merge medio
13h 40m
PR unite (30g)
17

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 Open-MBEE/sysml_view_editor

Tutte le issue di Open-MBEE/sysml_view_editor

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.