Accessing result of task in an action chain can get very ugly
Open
Nobody has claimed this yet.
feature
status:under discussion
workflows: action chain
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
e.g. format: "{{execution.result.tasks.1.result.result}}"
Its obviously brittle, confusing and extremely error prone.
Perhaps a nice filter of the form {{ execution.result | task_result(<task_name>) }}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how action-chain results are represented and how format expressions such as {{execution.result.tasks.1.result.result}} are rendered. Define the task-name lookup behavior and its expected handling before implementing the proposed task_result(<task_name>) filter; done means users can access a task result without positional nesting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100