StackStorm / StackStorm/orquesta
Allow YAQL/Jinja expression in join
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 111
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Currently, join can either be all or an integer that represents number of incoming edges with examples being join: all or join: 3. There are cases where the number of incoming edges need to be determined dynamically and join does not currently accept YAQL or Jinja expression.
Contributor guide
No contributing guide indexed for this repository
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 locating the code path that parses and evaluates the workflow join field. Verify how join: all and integer values are handled, then define the expected behavior for YAQL or Jinja expressions that determine the incoming-edge count; done means dynamic expressions are accepted without breaking the existing forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100