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

未关闭
#17 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
react, typescript
领域
design, frontend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
2
派生
0
平均合并
13 小时 40 分钟
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Open-MBEE/sysml_view_editor 的其他 Issue

查看 Open-MBEE/sysml_view_editor 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。