Render analysis and verification cases with their usage context and evidence pointers

Aperta
#17 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript
Ambito
design, frontend

Direzione di ricerca

Start by reviewing the linked WP26 feedback report and the model files under examples/adcs/model_v2 at the reported revision; the report says its observation was not independently reproduced and does not identify the deployed commit. Locate the GeneralView case renderer and real-engine regression tests, then verify the cold case-filter fixture and typed evidence usage. Done means a documented, bounded renderer covers supported links and pointer values, identifies unsupported constructs, preserves declaration versus result distinctions, and passes those regressions.

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

Descrizione

enhancement

Source and status

WP26 feedback report — Bug 4; suggestion 1; feature F-5. 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

Filters admitting analysis or verification cases selected an unavailable case renderer. Overview could show boxes, but did not provide a coherent case/subject/objective/verify/attribute-value view. Case rendering is an acknowledged capability gap.

Reproduction / requested workflow

  1. Import a model containing calculation, analysis and verification definitions/usages.
  2. Open a GeneralView filtered by CalculationDefinition or AnalysisCaseDefinition, then one filtered by VerificationCaseDefinition.
  3. Inspect an exposed verification usage typed by an evidence case with String pointer attributes.

Acceptance / investigation criteria

  • Define and document a bounded case renderer for definitions and usages.
  • Show supported subject, objective and verify links plus authored pointer values; clearly identify unsupported constructs.
  • Preserve declaration-versus-executed-result distinctions.
  • Cover the report’s cold case-filter fixture and a typed evidence usage with real-engine regressions.

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.