Investigate duplicate-name rejection for verify targets with the same short name
维护者通常 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 内容生成。
描述
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
- Define separate concerns c1 and c2, each owning r1 : R1.
- Define W with an empty objective.
- Apply verification ev2 : W { objective { verify c1.r1; verify c2.r1; } }.
- 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
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
Open-MBEE/sysml_view_editor 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 15/100
Open-MBEE/sysml_view_editor#35 ·
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 25/100
Open-MBEE/sysml_view_editor#34 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
Open-MBEE/sysml_view_editor#33 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 55/100
Open-MBEE/sysml_view_editor#32 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
Open-MBEE/sysml_view_editor#31 ·
维护者通常 1 天内回复
查看 Open-MBEE/sysml_view_editor 的全部 Issue
相似的 Issue
-
area: batch
难度 2/5 1-3 小时 新手友好度 75/100
inabagumi/shinju-date#7294 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 68/100
streaming-video-technology-alliance/common-media-library#700 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
vercel-labs/ui#809 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 67/100
KrisCris/village-in-the-shade-guide#75 ·
维护者通常 1 天内回复
-
bot:ai-assisted component:platform-js status:untriaged
难度 1/5 1 小时以内 新手友好度 74/100
midnightntwrk/platform-js#38 ·