Render concern stakeholder bindings to their bound parts

Aperta
#27 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript, wasm

Direzione di ricerca

Start with the linked feedback report and the model files under examples/adcs/model_v2 at the reported revision; identify the editor entry point that renders the stakeholders view and how it resolves model bindings. Verify the binding meaning with the engine, then trace edge drawing and source navigation for repeated names and distinct concern usage contexts. Done means supported bindings point to the correct part or usage, and unresolved or unsupported bindings are explained; preserve drafts and the last valid model while recording the exact engine and build identity.

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

Descrizione

enhancement

Source and status

WP26 feedback report — Feature F-4. 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 stakeholder parameter appeared in an Overview, but its binding to a model part did not, although other model bindings rendered.

Reproduction / requested workflow

  1. Import a concern with stakeholder :>> s = sponsor.
  2. Expose the concern and stakeholder/part context in the stakeholders view.
  3. Inspect whether the resolved binding is drawn.

Acceptance / investigation criteria

  • Verify the binding’s resolved meaning with the engine.
  • Draw supported binding edges to the correct part/usage identity, with source navigation.
  • Explain unsupported or unresolved bindings rather than implying an absent relationship.
  • Cover repeated names and distinct concern usage contexts.

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.