Investigate inherited-name rejection for verify relationships in typed verification objectives

Aperta
#21 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
32/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript, wasm

Direzione di ricerca

Start with the linked WP26 feedback report, Bug 8, and the model files at the reported revision in examples/adcs/model_v2. Reproduce the workflow with both engines, recording their exact versions and diagnostics, then check the SysML naming rules and trace whether rejection comes from editor normalization, the local bridge, or the upstream engine. Done means a confirmed fix or an actionable diagnostic, with unapplied drafts and the last valid model preserved.

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

Descrizione

question

Source and status

WP26 feedback report — Bug 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

A verification usage objective reportedly rejected verify c1.r1 as a duplicate inherited name when its type already declared verify requirement r1 : R1. Another toolkit accepted the text; that disagreement does not establish conformance.

Reproduction / requested workflow

  1. Define V with objective { verify requirement r1 : R1; }.
  2. Define concern c1 containing r1 : R1.
  3. Apply verification ev : V { objective { verify c1.r1; } }.
  4. Capture both engines’ exact versions and diagnostics.

Acceptance / investigation criteria

  • Resolve expected naming/redefinition behavior against authoritative SysML rules.
  • Locate responsibility in editor normalization, local bridge or upstream engine.
  • Fix confirmed rejection, or give an actionable diagnostic including inherited owner/member and a valid modeling alternative.
  • Retain last valid source/model on rejection.

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.