Charles Bochet
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.
8 lines
220 B
TypeScript
8 lines
220 B
TypeScript
import { gql } from '@apollo/client';
|
|
|
|
export const UPDATE_LOGIC_FUNCTION_SOURCE = gql`
|
|
mutation UpdateLogicFunctionSource($input: UpdateLogicFunctionSourceInput!) {
|
|
updateLogicFunctionSource(input: $input)
|
|
}
|
|
`;
|