Compose a Model pane header with independent representation selection
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
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
ModelPaneHeaderwith 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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Open-MBEE/sysml_view_editor
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 15/100
Open-MBEE/sysml_view_editor#35 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Open-MBEE/sysml_view_editor#34 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Open-MBEE/sysml_view_editor#33 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
Open-MBEE/sysml_view_editor#32 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Open-MBEE/sysml_view_editor#31 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Open-MBEE/sysml_view_editor
Issues similares
-
area: batch
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
inabagumi/shinju-date#7294 ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
streaming-video-technology-alliance/common-media-library#700 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
vercel-labs/ui#809 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
KrisCris/village-in-the-shade-guide#75 ·
Los mantenedores suelen responder en 1 día
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
midnightntwrk/platform-js#38 ·