Clarify and verify exposure/filter scope across diagram representations

Abierto
#19 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start with the linked WP26 feedback report and model files at the cited revision, then identify the editor’s view and filter entry points and the OpenSysML/SysML Toolkit contracts. Reproduce the Sat comparison with the exact engine and build recorded, separating exposure, filter membership, and representation expansion. Done means documenting supported differences and adding focused fixtures for any confirmed inconsistency.

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

Descripción

question

Source and status

WP26 feedback report — Bug 6; suggestion 8. 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 report expected a consistent element set, but a filtered structural view of Sat drew one node while an unfiltered Overview drew Sat and its three children. Different filters/projections may legitimately differ; correctness is not established by these screenshots alone.

Reproduction / requested workflow

  1. Apply the report’s minimal Sat model.
  2. Compare GeneralView with filter @SysML::PartDefinition; expose Demo::Sat against an unfiltered GeneralView exposing Demo::Sat.
  3. Repeat with otherwise identical exposure/filter inputs across supported representations.

Acceptance / investigation criteria

  • Separate exposure membership, filter membership and representation expansion.
  • Establish intended behavior from SysML and engine contracts before changing semantics.
  • Document supported differences and fix any confirmed inconsistency with focused fixtures.

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.

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.