The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 11, 2026 5:56pm

PR Summary

Low Risk
Narrow visibility-filter change with a focused regression test; no auth, data, or API surface changes.

Overview
Fixes a duplicate "Table ID" row on the workflow canvas when a Table block uses advanced (manual) table selection. Blocks that merge trigger subBlocks (e.g. table_new_row) can include a second manualTableId with mode: 'trigger-advanced'; preview and layout logic only hid mode === 'trigger', so that copy still appeared outside trigger mode.

Canvas preview (workflow-block.tsx) and autolayout height estimation (autolayout/utils.ts) now use isTriggerModeSubBlock, which treats both trigger and trigger-advanced as trigger-only—aligned with the editor sidebar’s trigger visibility rules.

Adds a regression test in utils.test.ts: for a table-like config with trigger-spread duplicates, getBlockMetrics yields the same height for basic vs advanced canonical mode.

^{Reviewed by Cursor Bugbot for commit 626cd78. Configure here.}

Greptile Summary

This PR fixes a UI bug where switching the Table block's table field to "advanced" (manual) mode caused a duplicate "Table ID" row to appear in the canvas block preview. The root cause was that the canvas filter and autolayout row estimator only excluded mode === 'trigger' subblocks, missing mode === 'trigger-advanced' subblocks that are spread from the trigger definition.

• Replaces hand-rolled block.mode === 'trigger' checks in workflow-block.tsx and autolayout/utils.ts with the canonical isTriggerModeSubBlock helper (which covers both 'trigger' and 'trigger-advanced'), matching what isSubBlockVisibleForTriggerMode already did in the editor sidebar.
• Adds a regression test in utils.test.ts that constructs a table-like config with trigger-spread duplicate subblocks and asserts that basic and advanced canonical modes produce identical row heights.

Confidence Score: 5/5

Safe to merge — the change is a targeted two-site substitution replacing an incomplete mode check with the canonical helper, backed by a new regression test that fails without the fix.

Both changed call sites in workflow-block.tsx and autolayout/utils.ts are straightforward replacements of block.mode === 'trigger' with the already-existing isTriggerModeSubBlock helper, which has been in use in the editor sidebar. The fix is consistent across canvas preview and autolayout estimation. The new test exercises the exact failure scenario described in the PR and correctly asserts height parity between basic and advanced modes. No new state management, API calls, or side effects are introduced.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Block subBlocks config spread\nfrom trigger definition] --> B{effectiveTrigger?}
    B -- Yes --> C{isPureTriggerBlock?}
    C -- Yes --> D["isTriggerModeSubBlock(block)\nOR !block.mode"]
    C -- No --> E["isTriggerModeSubBlock(block)"]
    D -- false --> F[Exclude from canvas preview]
    E -- false --> F
    D -- true --> G[Keep - proceed to mode/condition checks]
    E -- true --> G
    B -- No --> H["isTriggerModeSubBlock(block)\n= mode==='trigger' OR mode==='trigger-advanced'"]
    H -- true --> F
    H -- false --> G
    G --> I["isSubBlockVisibleForMode()"]
    I -- visible --> J["evaluateSubBlockCondition()"]
    J -- pass --> K[Render row in canvas preview]
    I -- not visible --> F
    J -- fail --> F

    style F fill:#f96,stroke:#c00
    style K fill:#6c6,stroke:#060

_{Reviews (1): Last reviewed commit: "fix(workflow-block): exclude trigger-adv..." | Re-trigger Greptile}