How do we improve the debugging experience for edge conditions?

[christad92]

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

[josephjclark]

I'm fairly sure that edge conditions are valid and don't need to be represented as nodes.

But yeah, debugging them is quite hard. Most of our debugging experience is pretty poor right now tbh.

In the long run I'd like to be able to drop a breakpoint and allow live debugging in the CLI and maybe even Lightning.

I'd like to introduce helper functions for edge conditions (see https://github.com/OpenFn/kit/issues/511). If we do this, we can probably add lots of automated logging.