ai-refactor(flow): 调整抽象流程节点实现和依赖路径

- 修改 AbstractProcessNode 中 ProcessContext 的命名空间引用为 app\flow\context\ProcessContext
- 引入 app\flow\vo\CanHandleResult 用于节点处理结果表示
- 更新前置策略执行后对成功状态的判断,改为调用 isSuccess() 方法
- 增加日志记录细节,便于调试策略执行中断时的错误信息
- 优化代码注释,提升代码可读性和维护性
This commit is contained in:
zimoyin
2026-03-11 00:48:10 +08:00
parent d303f3501f
commit e040fccba6
45 changed files with 819 additions and 2718 deletions
+13 -10
View File
@@ -3,9 +3,10 @@
namespace app\flow\nodes;
use app\config\Config;
use app\flow\DbOperationType;
use app\flow\ProcessContext;
use app\flow\VoiceMessage;
use app\flow\enum\DbOperationType;
use app\flow\context\ProcessContext;
use app\flow\enum\VoiceMessage;
use app\flow\vo\CanHandleResult;
/**
* 虚拟清洗机节点
@@ -32,20 +33,22 @@ class VirtualWashMachineNode extends AbstractProcessNode
/**
* 判断当前节点是否能处理该步骤
*/
public function canHandle(ProcessContext $context): bool
public function canHandle(ProcessContext $context): CanHandleResult
{
// 如果内镜未取出
if ($context->isInStorage) {
$context->expectedNextStep = VoiceMessage::PLEASE_SWIPE_STORAGE_OUT;
return false;
if ($context->getStorage()->isInStorage) {
return CanHandleResult::no(VoiceMessage::PLEASE_SWIPE_STORAGE_OUT);
}
// 如果不是机洗
if ($context->readerType !== MachineWashNode::getName()) {
return false;
if ($context->getReader()->type !== MachineWashNode::getName()) {
return CanHandleResult::no();
}
return Config::getInstance()->enableVirtualCleanerParser;
if (Config::getInstance()->enableVirtualCleanerParser) {
return CanHandleResult::yes();
}
return CanHandleResult::no();
}
/**