Name a control flow
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
One new feature that would be fine : give a (optional) name to a control flow.
Since you can't rely on the filters order, that is every time you edit a control flow, filters order may change....
Alternatively, don't change the initial order. For instance, one might start with a tag filter which would be significant to identify the control flow. But as of now, with this changing order of filters...
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
The issue names no files, tests, or entry points. Start by locating the control-flow implementation and its filter serialization or editing path; done means control flows can be identified reliably by an optional name or retain a stable, documented filter order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100