Charles BochetandGitHub
67a98f77e3
# Refactor workflow–logic function interaction ## Why Workflow code steps and standalone logic functions shared the same build layer and DB layer, which blurred two use cases: code steps belong to a workflow version; standalone functions are deployable units. That made workflow code steps harder to own and evolve. ## Goal Treat code steps as **workflow-owned**: build and run them in workflow context, and expose workflow-scoped APIs so the editor can load, test, and save code step source without going through the generic logic-function layer.
20 lines
972 B
TypeScript
20 lines
972 B
TypeScript
import { Module } from '@nestjs/common';
|
|
|
|
import { WorkspaceManyOrAllFlatEntityMapsCacheModule } from 'src/engine/metadata-modules/flat-entity/services/workspace-many-or-all-flat-entity-maps-cache.module';
|
|
import { LogicFunctionModule } from 'src/engine/metadata-modules/logic-function/logic-function.module';
|
|
import { CodeStepBuildModule } from 'src/modules/workflow/workflow-builder/workflow-version-step/code-step/code-step-build.module';
|
|
import { WorkflowQueryHookModule } from 'src/modules/workflow/common/query-hooks/workflow-query-hook.module';
|
|
import { WorkflowCommonWorkspaceService } from 'src/modules/workflow/common/workspace-services/workflow-common.workspace-service';
|
|
|
|
@Module({
|
|
imports: [
|
|
WorkflowQueryHookModule,
|
|
LogicFunctionModule,
|
|
WorkspaceManyOrAllFlatEntityMapsCacheModule,
|
|
CodeStepBuildModule,
|
|
],
|
|
providers: [WorkflowCommonWorkspaceService],
|
|
exports: [WorkflowCommonWorkspaceService],
|
|
})
|
|
export class WorkflowCommonModule {}
|