fix(blocks): render tooltip field in sub-block label

[minijeong-log]

Summary

• SubBlockConfig.tooltip was typed in blocks/types.ts (added in commit 8215a81) but never rendered in sub-block.tsx
• Adds an Info icon next to the field label that shows the tooltip text on hover
• Reuses the existing Tooltip.Root/Trigger/Content pattern already present in the same file

Changes

apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/sub-block/sub-block.tsx

• Add Info to lucide-react imports
• Render tooltip icon after the required asterisk in renderLabel

Test plan

• Add tooltip: 'some help text' to a subBlock in any block config
• Open the workflow editor and find that block
• Verify an Info icon appears next to the field label
• Hover over the icon and verify the tooltip text appears

Fixes #4071

[cursor]

PR Summary

Low Risk
Small, UI-only change limited to label rendering and tooltip triggers with minimal behavioral impact.

Overview
Sub-block labels now render SubBlockConfig.tooltip by showing an Info icon next to the field title that displays the tooltip text on hover using the existing Tooltip pattern.

Also makes the tooltip trigger wrappers keyboard-focusable (adds tabIndex/role) for the new tooltip icon and the existing invalid-JSON warning icon.

^{Reviewed by Cursor Bugbot for commit 4891982. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 9, 2026 7:13am

[greptile-apps]

Greptile Summary

This PR wires up the previously unrendered SubBlockConfig.tooltip field by adding an Info icon tooltip trigger inside the renderLabel function in sub-block.tsx, reusing the same Tooltip.Root/Trigger/Content pattern already present in the file for the AlertTriangle JSON-validation indicator.

Confidence Score: 5/5

Safe to merge — minimal, well-scoped change that follows established patterns in the file.

The only finding is a P2 accessibility suggestion (missing tabIndex on the tooltip trigger span), which also applies to the pre-existing AlertTriangle trigger. No logic, data, or security concerns.

No files require special attention.

Vulnerabilities

No security concerns identified.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/sub-block/sub-block.tsx	Adds conditional Info-icon tooltip rendering in renderLabel when config.tooltip is set; follows the existing AlertTriangle tooltip pattern exactly.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[renderLabel called] --> B{config.title?}
    B -- No --> Z[return null]
    B -- Yes --> C{config.type === 'switch'?}
    C -- Yes --> Z
    C -- No --> D[Render Label container]
    D --> E[Render title text]
    E --> F{required?}
    F -- Yes --> G[Render asterisk span]
    F -- No --> H
    G --> H{config.tooltip?}
    H -- Yes --> I[Render Info icon + Tooltip.Root]
    H -- No --> J
    I --> J[Render labelSuffix]
    J --> K{code + JSON + invalid?}
    K -- Yes --> L[Render AlertTriangle + Tooltip.Root]
    K -- No --> M[Render action buttons]
    L --> M

Loading

_{Reviews (1): Last reviewed commit: "fix(blocks): render tooltip field in sub..." | Re-trigger Greptile}

[greptile-apps]

Tooltip trigger not keyboard-accessible

The <span> wrapping the Info icon has no tabIndex, so keyboard-only users cannot focus it to trigger the tooltip. Adding tabIndex={0} (and a matching role) makes it reachable via Tab. Note: the existing AlertTriangle trigger below uses the same pattern, so this affects both.

Suggested change

	<Tooltip.Trigger asChild>
	<span className='inline-flex'>
	<Info className='h-3 w-3 flex-shrink-0 cursor-pointer text-muted-foreground' />
	</span>
	<span className='inline-flex' tabIndex={0} role='button'>

[minijeong-log]

Fixed in:

• e2b2206 — added tabIndex={0} and role='button' to the Info tooltip trigger
• 4891982 — also applied the same fix to the existing AlertTriangle trigger as noted