fix(serializer): required-field validation now respects sub-block visibility

[icecrasher321]

Summary

Required-field validation now respects sub-block visibility (mode + conditions), so “File URL” is only required in URL mode and not in Upload Files.

Type of Change

• Bug fix

Testing

Use File Block --> Upload Files should not throw "is missing File URL" error.

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 GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sim	Ready	Preview	Comment	Sep 11, 2025 2:46am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Sep 11, 2025 2:46am

[greptile-apps]

Greptile Summary

This PR fixes a critical validation bug in the File Block functionality where users were incorrectly getting "File URL is missing" errors even when they selected the "Upload Files" mode. The File Block supports two input methods: entering a file URL or uploading files directly. Previously, the validation logic was too simplistic and would always require the filePath parameter regardless of which input method the user selected.

The fix implements sophisticated conditional validation logic in the serializer (apps/sim/serializer/index.ts) that mirrors the UI's visibility behavior. The new validation system evaluates both sub-block mode visibility and conditional requirements before determining if a field should be validated as required. Specifically, it checks if inputMethod is set to 'url' before requiring the filePath parameter, ensuring that file upload mode doesn't trigger URL validation errors.

The implementation adds a complex condition evaluation system that handles nested conditions with 'and' clauses and supports both function and object-based conditions. This change aligns backend validation with frontend UI behavior, creating a consistent user experience where validation only occurs for fields that are actually visible and relevant to the current user's selections.

Confidence score: 4/5

• This PR addresses a clear UX bug with well-defined scope and proper conditional logic implementation
• Score reflects solid implementation with comprehensive condition handling, though the complex nested logic could benefit from additional testing
• Pay close attention to the condition evaluation logic in the serializer, particularly the nested evalCond function and 'and' clause handling

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}