驳回节点的画法(前端):被驳回的那一步画成「被驳回」,不画成失败

服务端给被驳回的那一步的 node.failed 带上了 reason=rejected(上一个提交)。界面上读 node.failed 的几处都认它
(05-已知遗留 (a)、总方案 X9:驳回是人的决定,不是故障),没有 reason 的老运行照旧画失败:

- run/decode:问数据过程、记录页、画布右栏的时间线里,这一步状态 rejected(StepStatus 加一种),副标题写谁驳回、
  备注(REJECTED_TEXT.step),原话放展开里;不是 error 级别,不当成出错
- run/trace、run/derive:NodeState 加 rejected;那一段收成 rejected,不记成「失败的节点」,下游是「未到达」不是
  「被阻断」;回放投影同样是 rejected
- 画布节点卡:rejected 一种读数(耗时 + 原话第一句,整句悬停),中性色、停止剪影,不挂失败红框、不抖动;小地图、
  运行胶囊的计数、时间轴泳道认得它;记录页航迹的节点卡写「被驳回:原话」
- check-decode、check-run-states 各加一段:新旧两种形状
This commit is contained in:
ThearchyHelios
2026-10-16 19:42:11 +08:00
parent eb578cad34
commit 4c7c0cf283
14 changed files with 181 additions and 13 deletions
+1 -1
View File
@@ -91,7 +91,7 @@ export function replayTraceCached(trace: Trace, at: number, graph: GraphLike): T
}
const state = p?.state ?? 'idle'
// 人工审批的通过 / 驳回只记在节点上,不在段上:它结束了就用节点上的
const finished = state === 'done' || state === 'failed'
const finished = state === 'done' || state === 'failed' || state === 'rejected'
const decided = taken.length ? taken : finished ? n.taken ?? [] : []
nodes[id] = {
...n, state, count: p?.count ?? 0, iteration: p?.iteration, taken: decided,