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

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

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.

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

描述

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.

主要语言
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 摘要。