improvement(copilot): add subblock enums to block metadata

[Sg312]

Summary

Adds subblock enums to give the copilot more context for each block

Type of Change

• Bug fix - bug fix/improvement

Testing

Manual testing

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 5, 2025 1:54am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 5, 2025 1:54am

[greptile-apps]

Greptile Summary

This PR enhances the copilot's understanding of block configurations by adding comprehensive subblock metadata extraction. The change introduces a new processSubBlocks function that extracts detailed UI configuration properties from block subBlocks, including dropdowns, sliders, inputs, and other UI elements. A helper function resolveSubBlockOptions safely handles both static arrays and function-based options configurations.

The implementation adds extensive property mapping to capture UI element details like labels, descriptions, options, default values, and conditional visibility settings. Special hardcoded metadata is included for 'loop' and 'parallel' blocks since these core workflow control blocks aren't in the standard registry but are essential for the copilot to understand.

The main metadata extraction flow is enhanced to include additional block properties (longDescription, category, bgColor, hideFromToolbar) and integrates the new subblock processing. This provides the copilot AI assistant with complete visibility into block UI structure, enabling it to better assist users with workflow configuration by understanding all available block capabilities and their configuration options.

Confidence score: 4/5

• This PR is safe to merge with minimal production risk as it primarily adds metadata extraction without changing core functionality
• Score reflects comprehensive implementation with proper error handling, though the large amount of hardcoded metadata introduces some maintenance overhead
• Pay close attention to the hardcoded SPECIAL_BLOCKS_METADATA section for accuracy and completeness

_{1 file reviewed, 1 comment}

_{Edit Code Review Bot Settings | Greptile}