Improve UX around "disabling" first edge
Open
Nobody has claimed this yet.
needs detail
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
The concept of disabling edges gets muddy on the first edge, where there is a dependency on the Firing Trigger being disabled. This leads to user confusion (even internally).
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
No file, test, or entry point is identified in the issue. First clarify the intended behavior and wording for disabling the first edge, then trace the existing first-edge and Firing Trigger flow; done means the dependency is understandable and the agreed UX is covered by tests or review.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100