Skip to content

fix(approval): 退回候选节点改用后端执行历史列表 (#270) - #78

Merged
xlorne merged 2 commits into
devfrom
feature/issue-270-return-node-control
Nov 16, 2026
Merged

xlorne merged 2 commits into
devfrom
feature/issue-270-return-node-control

Conversation

@xlorne

@xlorne xlorne commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

问题

PC / 移动端退回弹框从流程定义的全量节点(flow.nodes)中截取到当前节点,导致(issue #270):

  • 当前节点在条件/并行块内时匹配不到,候选退化为全部节点,可以选到当前节点之后的节点;
  • 未被经过的分支节点也会出现在候选里;
  • 顺序是定义顺序(A、B),而不是最近优先(B、A)。

改动

  • flow-types:FlowContent 新增可选字段 backNodes(后端按执行历史下发,最近优先)。
  • flow-approval-presenter:新增 buildReturnNodeOptions,优先使用 backNodes;backNodes 为空数组表示明确不可退回(如开始节点),不再回退;仅当旧版后端缺失该字段时保留原有按定义顺序截取的兼容逻辑。
  • flow-pc-approval / flow-mobile-approval:return-view 改用该工具,不再自行截取流程定义节点。
  • 新增 tests/return-nodes.test.ts 与 changeset。

验证

  • pnpm -F @coding-flow/flow-approval-presenter test:102 个用例通过(含新增 5 个)
  • pnpm run build:flow-pc-approval、pnpm run build:flow-mobile:构建通过
  • test:flow-pc-approval / test:flow-mobile-approval 中 act(...) is not supported in production builds of React 的失败为本地环境既有问题,dev 基线同样失败(同一文件、同一数量)

Closes #270

PC / 移动端退回弹框此前从流程定义的全量节点(nodes)中截取到当前节点,
当前节点不在顶层节点列表时(条件/并行块内)会退化为全部节点,能选到
当前节点之后的节点,且顺序为定义顺序(A、B)而非最近优先(B、A)。

- flow-types 新增可选字段 backNodes(后端按执行历史下发,最近优先)
- 新增 buildReturnNodeOptions(flow-approval-presenter):优先使用
  backNodes;为空数组表示明确不可退回,不再回退;旧版后端缺失该字段时
  保留原有按定义顺序截取的兼容逻辑
- PC / 移动端 return-view 改用该工具,不再自行截取流程定义节点
- 补充 return-nodes 单元测试与 changeset

Closes #270
- changeset version:fixed 模式下全部 @coding-flow/* 包统一 0.2.20 -> 0.2.21
  (flow-types / flow-core / flow-icons / flow-approval-presenter /
  flow-pc-ui / flow-pc-form / flow-pc-approval / flow-mobile-ui /
  flow-mobile-form / flow-mobile-approval / flow-design)
- 生成各包 0.2.21 CHANGELOG(含 Updated dependencies 段)
- 删除已消费的 .changeset/issue-270-return-back-nodes.md
- 包间依赖使用 workspace:*,pnpm-lock.yaml 无需变更
@xlorne
xlorne merged commit 1c20aa9 into dev Nov 16, 2026
1 check passed
@xlorne
xlorne deleted the feature/issue-270-return-node-control branch November 16, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant