Visualize calculation dependencies and their model consumers

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the WP26 feedback report and the model files in examples/adcs/model_v2 at the cited revision; the issue does not identify the deployed engine or build. Trace how the CalculationDefinition-only filter produces the reported view, then map supported invocations and references while preserving resolved identities. Done means documenting unavailable relationships and distinguishing declared dependencies from evaluated quantities, with drafts and the last valid model preserved.

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

描述

enhancement

Source and status

WP26 feedback report — Suggestion 5; Bug 4 workaround. 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 CalculationDefinition-only workaround reportedly produced 32 boxes and no edges, hiding how design variables, calculation invocations and output quantities connect.

Reproduction / requested workflow

  1. Open the reported metrics view using the CalculationDefinition-only filter.
  2. Compare invoked calculations and attribute consumers with displayed edges.

Acceptance / investigation criteria

  • Define a bounded, source-backed dependency projection for supported invocations and references.
  • Retain resolved input/output/usage identity rather than connecting by names alone.
  • Explain unavailable relationships and distinguish declared dependencies from evaluated quantities.

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 摘要。