Draw mermaid flowchart Version 1

[abjjabjj]

Try this in jupyter

from concrete.mermaid import FlowchartDirection
from concrete.operators import *
from concrete.projects import DAGNode, Project


project = Project()
nodes = [project.add_node(node) for node in [
    DAGNode("fee", "chat", Operator(), {"message": "Hello World!"}),
    DAGNode("fi", "ask_question", Developer(), {"context": "You pass butter."}),
    DAGNode("fo", "answer_question", Executive()),
    DAGNode("fum", "generate_summary", Executive()),
]]
edges = [
    project.add_edge("fee", "fo", "context"),
    project.add_edge("fi", "fo", "question"),
    project.add_edge("fee", "fum", "summary"),
    project.add_edge("fo", "fum", "implementation"),
]

print(project.draw_mermaid())

Paste to Mermaid Live Editor

See the magic

Needs tests but it's alive

• Few styling options, i.e. title and direction of graph.
• Few subgraph options, i.e. can set start and end nodes.
• Implemented generic BFS and source/sink finders for directed graphs (note not acyclic constrained)
  • Hint hint means visualization should work on unfinished DAGProjects (I haven't actually tested this yet)

[abjjabjj]

end_nodes functionality is bugged (but not feature breaking) because edge processing is done post-node processing

[abjjabjj]

so edge case (get it) is for parent node of end node, it will process all the edges on that layer of the BFS instead of just the one connecting parent to end

[abjjabjj]

actually there’s a bunch of other cases that will probably be buggy since there are no checks on end nodes

[abjjabjj]

e.g. all the end nodes could be upstream of the start nodes if graph is a DAG

[abjjabjj]

could change implementation to backtracking instead. I think that should solve the problems

[MichaelDeng03]

I think your link to mermaid live editor is borked - it seems to be linking to github diffs

[MichaelDeng03]

Otherwise, very neat!
Could you add a placeholder/templating to children nodes, it's not clear that answer_question can accept context/question.