Help users diagnose errors when building workflows
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When building workflows and there is an unresolved error in the path configuration, the save button becomes disabled with a red indicator. The blocks users from saving the workflow but there is also no way to tell what is wrong.
It would be great to indicate paths with errors or have a list of errors that can be clicked to open the configuration with error.
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 in the workflow builder's path-configuration validation and save-button error state; the issue does not name specific files or tests. Trace how unresolved path errors are represented and surfaced in the UI. Done means users can identify the erroneous path or open an error entry to reach its configuration before saving.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100