fix(input-format): resolution for blocks with input format fields#3012
Merged
icecrasher321 merged 3 commits intostagingfrom Jan 27, 2026
Merged
fix(input-format): resolution for blocks with input format fields#3012icecrasher321 merged 3 commits intostagingfrom
icecrasher321 merged 3 commits intostagingfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
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
|
Collaborator
Author
|
@cursor review |
Collaborator
Author
|
@cursor review |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolution should be consistent with input format and throwing InvalidFieldErrors, vs passing
Type of Change
Testing
Tested manually
Checklist