-
Notifications
You must be signed in to change notification settings - Fork 3.3k
fix(input-format): resolution for blocks with input format fields #3012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Greptile OverviewGreptile SummaryThis PR fixes input format field resolution for trigger blocks by ensuring custom Key Changes:
Issues Found:
Confidence Score: 3/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Executor as Block Executor
participant BlockData as getBlockSchema()
participant Normalize as normalizeInputFormatValue()
participant Schema as Block Output Schema
participant Resolver as Block Resolver
Note over Executor,Resolver: Field Resolution Flow
Executor->>BlockData: Get schema for trigger block
BlockData->>BlockData: Check if trigger in TRIGGERS_WITH_INPUT_FORMAT_OUTPUTS
alt Is input format trigger
BlockData->>Normalize: normalizeInputFormatValue(inputFormat)
Normalize-->>BlockData: Filtered input format fields (with value field preserved)
BlockData->>BlockData: Convert fields to OutputSchema
BlockData->>Schema: Merge base outputs + inputFormat fields
Schema-->>BlockData: Merged schema
else Standard trigger
BlockData->>Schema: Use block.outputs directly
Schema-->>BlockData: Standard schema
end
BlockData-->>Executor: Output schema
Note over Executor,Resolver: Later: Variable Resolution
Resolver->>Resolver: Resolve reference (e.g., <start.myField>)
Resolver->>Schema: Check if path exists in schema
alt Field in schema
Schema-->>Resolver: Field exists
Resolver-->>Executor: Return value
else Field not in schema
Schema-->>Resolver: Field missing
Resolver->>Resolver: Throw InvalidFieldError
end
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 files reviewed, 2 comments
|
@cursor review |
|
@cursor review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Summary
Resolution should be consistent with input format and throwing InvalidFieldErrors, vs passing
Type of Change
Testing
Tested manually
Checklist