@codemation/core-nodes 0.13.0 → 0.14.0

package/src/nodes/split.ts

@@ -13,10 +13,6 @@ export class Split<TIn = unknown, TElem = unknown> implements RunnableNodeConfig
   readonly type: TypeToken<unknown> = SplitNode;
   readonly execution = { hint: "local" } as const;
   readonly keepBinaries = true as const;
-  /**
-   * When splitting yields zero items for a batch, downstream single-input nodes still run once with an empty batch.
-   * Mirrors {@link MapData}'s empty-output behavior.
-   */
   readonly continueWhenEmptyOutput = true as const;
   readonly icon = "builtin:split-rows" as const;
   readonly id?: string;

package/src/nodes/testTrigger.ts

@@ -13,34 +13,13 @@ export interface TestTriggerOptions<TOutputJson> {
   readonly name?: string;
   readonly id?: string;
   readonly icon?: string;
-  /** Cap on simultaneous in-flight test cases for one suite run. Default: 4 (orchestrator). */
   readonly concurrency?: number;
   readonly credentialRequirements?: ReadonlyArray<CredentialRequirement>;
-  /**
-   * Free-form description of where the test cases come from. Shown in the node properties
-   * panel and the Tests-tab suite-detail header so authors revisiting the workflow six months
-   * later remember which mailbox / folder / fixture file the cases originate from.
-   */
   readonly description?: string;
-  /**
-   * Author callback that yields one item per test case. Items are dispatched as separate
-   * workflow runs by the TestSuiteOrchestrator, with `executionOptions.testContext` set.
-   * The provided context exposes credential resolution and an AbortSignal for cancellation.
-   */
   generateItems(ctx: TestTriggerSetupContext<TestTrigger<TOutputJson>>): AsyncIterable<Item<TOutputJson>>;
-  /**
-   * Optional resolver: extract a human-readable label from a yielded item. The orchestrator
-   * persists this on the run, so the Tests-tab tree-table shows e.g. "RFQ for batch 14"
-   * instead of an opaque runId. Typical use: `(item) => item.json.subject` for mailbox tests.
-   */
   caseLabel?(item: Item<TOutputJson>): string | undefined;
 }
 
-/**
- * Trigger config for a test fixture source. Drop one (or more) of these on the canvas alongside
- * a workflow's live triggers; clicking "Run tests" on the Tests tab invokes
- * {@link TestTriggerOptions.generateItems} via the TestSuiteOrchestrator.
- */
 export class TestTrigger<TOutputJson = unknown> implements TestTriggerNodeConfig<TOutputJson> {
   readonly kind = "trigger" as const;
   readonly triggerKind = "test" as const;

package/src/nodes/wait.ts

@@ -7,7 +7,6 @@ export class Wait<TItemJson = unknown> implements RunnableNodeConfig<TItemJson,
   readonly kind = "node" as const;
   readonly type: TypeToken<unknown> = WaitNode;
   readonly execution = { hint: "local" } as const;
-  /** Pass-through empty batches should still advance to downstream nodes. */
   readonly continueWhenEmptyOutput = true as const;
   readonly icon = "lucide:hourglass" as const;
   readonly id?: string;

package/src/nodes/webhookTriggerNode.ts

@@ -8,11 +8,6 @@ import type {
 import { node } from "@codemation/core";
 import { WebhookTrigger } from "./WebhookTriggerFactory";
 
-/**
- * HTTP webhooks are not registered in trigger setup. The host exposes a single catch-all route
- * (e.g. `/api/webhooks/:endpointPath`); the engine's catalog-backed webhook matcher resolves the
- * user-defined endpoint path to this workflow + node, then runs the workflow from this trigger.
- */
 @node({ packageName: "@codemation/core-nodes" })
 export class WebhookTriggerNode implements ExecutableTriggerNode<WebhookTrigger<any>> {
   readonly kind = "trigger" as const;

package/src/register.types.ts

@@ -14,19 +14,9 @@ import { FilterNode } from "./nodes/filter";
 import { SplitNode } from "./nodes/split";
 import { SwitchNode } from "./nodes/switch";
 
-/**
- * Registrar for built-in nodes. In a real project, this would use tsyringe's
- * container.registerSingleton(...). For the skeleton we keep it token-based:
- * the engine resolves node implementations by class token.
- */
 export function registerCoreNodes(container: Container): void {
-  // With class tokens, resolving registers happen via the DI container setup.
-  // This function exists as the standardized extension point.
   void container;
 
-  // Example: if using tsyringe, you'd do:
-  // tsyringeContainer.registerSingleton(IfNode, IfNode);
-  // ...
   void IfNode;
   void HttpRequestNode;
   void CallbackNode;

package/src/workflows/AIAgentConnectionWorkflowExpander.ts

@@ -5,9 +5,6 @@ import { AIAgentNode } from "../nodes/AIAgentNode";
 import { ConnectionCredentialNode } from "../nodes/ConnectionCredentialNode";
 import { ConnectionCredentialNodeConfigFactory } from "../nodes/ConnectionCredentialNodeConfigFactory";
 
-/**
- * Materializes connection-owned child nodes and {@link WorkflowDefinition.connections} for AI agent nodes.
- */
 export class AIAgentConnectionWorkflowExpander {
   constructor(
     private readonly connectionCredentialNodeConfigFactory: ConnectionCredentialNodeConfigFactory,