Distinguish rendering and inspection activity from unapplied source drafts
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript
调研方向
Start with Suggestion 11 in the linked WP26 feedback report and compare its reported observation with the current editor behavior; the issue says the deployed commit was not identified and the behavior has not been reproduced locally. Trace how toolbar/header status and Apply availability reflect source equality, engine work, failures, and recovery. Done means reproducing with exact operation and build identity and verifying that progress is distinct from unapplied drafts while preserving drafts and the last valid model.
由索引模型根据 Issue 内容生成。
描述
Source and status
WP26 feedback report — Suggestion 11; section 2 item 17. 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 transient behavior; no dedicated cold-reader screenshot retained. Not locally reproduced.
Problem
A reader who made no edit reportedly saw “Applied revision · draft pending”, “Working…” and an enabled Apply source transiently during browsing/restores. That wording made them think the source had changed.
Reproduction / requested workflow
- Restore or apply a project, then browse views and inspection surfaces without editing source.
- Observe toolbar/header state during engine work.
- Compare actual draft/applied source equality and transaction history.
Acceptance / investigation criteria
- Reproduce with exact operation/build identity; do not equate all busy state with source changes.
- Show rendering/inspection progress separately from genuine unapplied drafts.
- Enable Apply only under the intended source-state rules.
- Retain correct status during real edits, failures and recovery.
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 天内回复
-
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 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
Open-MBEE/sysml_view_editor#30 ·
维护者通常 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 ·