fix: Fixed configuring the entry point component #246
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
When configuring the Entry Point component in the workflow builder, users could not set default values for runtime inputs. The "Runtime Data" input field in the sidebar:
Displayed a plain text input that expected a string, but the underlying schema required a JSON object (z.record(z.string(), z.unknown())), causing validation errors like:
Workflow validation failed: [entry-point-...] inputOverrides: Component input validation failed: expected: "record", code: "invalid_type", path: ["__runtimeData"], message: "Invalid input: expected record, received"
Default values were ignored when clicking "Run" - the Run Workflow dialog always opened with empty fields, requiring users to re-enter values every time.
Solution
Before/After
Before: Single text field → validation error → Run dialog always empty
After: Individual fields per runtime input → proper object storage → Run dialog pre-populated with defaults
Testing
bun run testbun run lintbun run typecheckDocumentation
docs/guide.md) or checked that no updates are needed..ailogs when applicable.