Compose a Model pane header with independent representation selection

Cerrado
#42 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #46 de @rororowyourboat — fusionado

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
design, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
0
Merge medio
13 h 40 min
PR fusionados (30 d)
17

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

Todos los issues de Open-MBEE/sysml_view_editor

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.