Repository navigation
fix(assistant): 对话新建的需求不再套上项目默认 SOP - #5
Open
Robert0622 wants to merge 2 commits into
Open
Robert0622 wants to merge 2 commits into
Robert0622 wants to merge 2 commits into
Conversation
…ult SOP A new chat save that names no workflow, and a requirement created from a conversation workspace, now stay on sopMode none. Updating an existing issue is unchanged, and the prompt no longer says the platform already bound the generic backend SOP. Co-authored-by: Cursor <[email protected]>
Owner
Author
|
本提交的 13 项独立检查已通过。第 3 次运行中,GitHub 仍未能为 macOS 分配托管 runner,测试步骤数为 0。依赖该任务的 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3
复现与影响
在配置了默认「通用后端交付 SOP」的项目里,让对话先登记退款 CSV 的验收要求。原始修复覆盖自动写入,但用户在浏览器确认同一份无 SOP 的草稿时,新需求仍显示后端交付的全部节点。自动模式还有另一个问题。调用者明确指定套餐或多步流程链时,保存会清空这个选择。
修复
需求创建处理器在取得实际记录后,统一处理浏览器确认的草稿与助手自动写入。无 SOP 选择的对话新需求保存为
sopMode=none。明确指定的工作流、套餐或流程链得到保留,编辑已有需求沿用其原有选择。对话工作区自动登记需求也使用相同的无 SOP 状态。普通需求表单仍按项目设置使用默认流程。实测
在同一套 v0.4.0 测试数据库中,分别部署原 PR 和本次修改的服务端。用 Chromium 打开相同内容的对话草稿,点击确认,再从需求列表打开「执行进展」。
原 PR 保存了
workflowId=generic-backend-delivery。修复后重新读取持久化记录,得到sopMode=none和空工作流。界面显示「这条需求不走 SOP」,用户可以稍后手动选择。通过实际 MCP 和 HTTP 入口回归了确认与自动两种路径,覆盖默认选择、显式工作流、显式套餐、流程链和更新已有需求。新增用例在原提交上失败,在本次提交上通过。
另用真实模型在私有 GitHub 沙箱中完成了一个带单元测试的开发需求并创建 PR。重新读取关联需求,状态为
in_review、sopMode=none,工作流为空;交付列表包含本次 PR。组合复测
将四个修复的实际提交应用到 v0.4.0 后,再次从 Chromium 点击确认草稿。需求记录仍为
sopMode=none、空工作流,执行进展显示「这条需求不走 SOP」。当前提交的 CI
提交
bb3f23182cf3的 15 项 GitHub 检查全部通过,含 macOS。 查看检查记录