I have a plugin i was building which does something similar, if you like I will put it in a public repo to review?

Sure @cabljac

do you mind adding a testapp (js/testapps/graph) that demonstrates the graph library in action?

Is this directed to me or @debkanchan ? (also happy to add a test app with the plugin)

do you mind adding a testapp (js/testapps/graph) that demonstrates the graph library in action?

Sure. I'll do that once I figure out 1. tracing 2. how to make it run like run(graph)

Hey @pavelgj @debkanchan this morning I opened a draft, with the code from the plugin i made before, included a test app:

#649

@cabljac I read your PR. Tbh it's the most complete one so far. But I have one problem with this approach that I have also previously stated in discord.

The concept of edges is bit confusing imo. To me, each node should be able to dictate which node it wants to go next based on it's internal conditions. We should not be needing separate edges or even worse conditional edges. This only confuses new-comers and imo more verbose.

Ah interesting, I didn't consider this. I come from a math background where an edge is quite intuitive, but perhaps you're right and it could be confusing.

I guess any way you define a graph it will have implicit edges, and most graph related packages will deal with edges to run various algorithms.

Perhaps the main way to define an edge could be implicitly at the node.

One thing I like about having a graph as a layer above the actual flows is that they can just point at the flows, so one flow could serve several node instances.

I should share the UI demo I made for it on discord with you. I'm away at the moment but will do when I get a chance. We should also move this to a separate repo probably. I could create one if you want, and invite you?

This pr has been moved to TheFireCo/genkit-plugins#117