Investigate duplicate-name rejection for verify targets with the same short name

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

Direzione di ricerca

Start with the referenced WP26 feedback report, Bug 9, and the model files at the reported revision in examples/adcs/model_v2. Compare exact engine versions, relationships, and diagnostics for the reproduction workflow, then check relationship naming semantics against the standard before considering validation changes. Done means a confirmed collision is fixed without merging distinct targets, or a valid rejection identifies the member and earlier declaration and explains an alternative.

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

Descrizione

question

Source and status

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

An objective with verify c1.r1 and verify c2.r1 reportedly produced duplicate-owned-member errors without identifying the conflicting member. Another toolkit accepted it.

Reproduction / requested workflow

  1. Define separate concerns c1 and c2, each owning r1 : R1.
  2. Define W with an empty objective.
  3. Apply verification ev2 : W { objective { verify c1.r1; verify c2.r1; } }.
  4. Compare exact engine versions, relationships and diagnostics.

Acceptance / investigation criteria

  • Establish valid relationship naming semantics against the standard before modifying validation.
  • Fix any confirmed incorrect collision without merging distinct targets.
  • If rejection is valid, identify the member and earlier declaration and explain a valid alternative.
  • Preserve the report’s rename workaround as a workaround, not proof of intended semantics.

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.