How do we improve the debugging experience for edge conditions?
Open
Nobody has claimed this yet.
discussion
question
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Today, we add conditions to edges which make them behave like nodes/steps and when conditions fail, we are not able to properly debug the edge even though there is a edgeConditionError printed in the logs.
We need to think about a way to debug these:
- do we make them nodes/steps?
- Can we inspect the edges from the inspectors?
other ideas?
@stuartc @josephjclark
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 files, tests, or entry points are named. Begin by tracing how failed edge conditions produce the edgeConditionError log and how inspectors represent workflow edges; done means agreeing on and documenting a concrete debugging approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100