Investigate inherited-name rejection for verify relationships in typed verification objectives
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 32/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript, wasm
调研方向
Start with the linked WP26 feedback report, Bug 8, and the model files at the reported revision in examples/adcs/model_v2. Reproduce the workflow with both engines, recording their exact versions and diagnostics, then check the SysML naming rules and trace whether rejection comes from editor normalization, the local bridge, or the upstream engine. Done means a confirmed fix or an actionable diagnostic, with unapplied drafts and the last valid model preserved.
由索引模型根据 Issue 内容生成。
描述
Source and status
WP26 feedback report — Bug 8. 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
A verification usage objective reportedly rejected verify c1.r1 as a duplicate inherited name when its type already declared verify requirement r1 : R1. Another toolkit accepted the text; that disagreement does not establish conformance.
Reproduction / requested workflow
- Define V with objective { verify requirement r1 : R1; }.
- Define concern c1 containing r1 : R1.
- Apply verification ev : V { objective { verify c1.r1; } }.
- Capture both engines’ exact versions and diagnostics.
Acceptance / investigation criteria
- Resolve expected naming/redefinition behavior against authoritative SysML rules.
- Locate responsibility in editor normalization, local bridge or upstream engine.
- Fix confirmed rejection, or give an actionable diagnostic including inherited owner/member and a valid modeling alternative.
- Retain last valid source/model on rejection.
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
-
难度 1/5 1-3 小时 新手友好度 83/100
gofish-graphics/gofish-graphics#1384 ·
维护者通常 1 天内回复
-
adapter bug
难度 2/5 1-3 小时 新手友好度 83/100
Olanetsoft/agent-lookout#353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
vicharanashala/vibe#1542 ·
维护者通常 1 天内回复
-
bug chore P2 size:XS
难度 2/5 1-3 小时 新手友好度 77/100
josephfung/curia#2666 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 84/100
devarshishimpi/codra#178 ·
维护者通常 1 天内回复