feat: add flow_input field to step_task_record for direct access to original input #554
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.

Add flow_input field to step_task_record for direct access to original run input
This PR adds a new
flow_inputfield to thestep_task_recordtype, which provides workers direct access to the original flow input without having to parse it from the constructedinputfield.Key changes:
flow_inputattribute to thepgflow.step_task_recordcomposite typestart_tasksfunction to populate this field with the original run inputflow_inputfield is correctly populated for:This enhancement simplifies worker implementation by providing direct access to the original flow input, which is particularly useful for context that needs to be available to all steps.