Compose a Model pane header with independent representation selection

Aperta
#42 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript
Ambito
design, frontend

Direzione di ricerca

Start by reading the implementation and acceptance checks for prerequisite issue #41, then inspect Diagram.tsx and the existing dataMode and selection flows. Map where named-view, exploration, metadata, and authoring controls currently live before deciding how ModelPaneHeader should own them. Done means the listed preservation, interaction, renderer, visual, and documentation checks pass without changing the workspace orchestration or engine contracts.

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

Descrizione

Design stage 2 of 4

Follow the agreed 2026-11-16 workbench product-design brief. Representation controls what Model displays; arrangement controls which Source/Model slots are visible.

Scope

  • Introduce ModelPaneHeader with a visibly labeled representation selector: Diagram, Requirements table, Traceability matrix.
  • Reuse existing dataMode; changing representation changes it only and preserves the outer arrangement.
  • Compose/relocate Diagram.tsx's existing named-view selector, exploration scope/representation controls, view metadata and supported New part/Connect ports actions. Leave one authoritative set of controls.
  • Show diagram-target controls only for Diagram. Project-level tables/matrices must not imply filtering by the active named view.
  • Keep table/matrix search/filter/sort/export in their owning content components.
  • Distinguish applied revision, unapplied drafts, current evaluation, temporary exploration and unavailable rendering. A pending draft must not imply the displayed model already reflects it.
  • Keep zoom, Fit, 100% reading, and lock actions on the diagram canvas only.

Acceptance

  • Representation changes preserve arrangement, active file/view, drafts, selection and project data.
  • Selecting a named view explicitly chooses Diagram representation without silently changing the active source file.
  • No duplicate named-view selector, exploration controls or authoring actions remain.
  • Requirement/table selection opens Inspector; source reveal remains a separate action with current-model and unchanged-draft guards from #38.
  • Evaluation/exploration actions, renderer mounting and busy/failure behavior retain their existing contracts.
  • Pointer/keyboard, requirements/exploration and preservation regressions plus reviewed desktop/narrow light/dark visuals pass.
  • Architecture/capability documentation reflects the implemented header ownership.

Related requirement: #34. Do not redesign workspace orchestration, engine contracts, persistence or introduce a plugin-like representation framework.

Implementation order

Depends on #41. Keep this stage reviewable independently and preserve the preceding stages' acceptance checks.

Lingua principale
TypeScript
Stelle
2
Fork
0
Merge medio
15h 5m
PR unite (30g)
15

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.