Add export and import method for graph #12

New issue

Open

opened 2026-06-06 22:02:09 +00:00 by linarphy · 3 comments

linarphy commented

2026-06-06 22:02:09 +00:00

Owner

This would allow to load a graph from a file, and to save the graph to a file.

Conversion format ideas:

dot (https://graphviz.org/doc/info/lang.html)
mermaid (https://mermaid.ai/open-source/intro/syntax-reference.html)
plantUML (https://plantuml.com)
RDF/XML (https://w3c.github.io/rdf-xml/spec/)
RDF/TURTLE (https://w3c.github.io/rdf-turtle/spec/)

One possible strategy would be to implement those conversion is to implement a convert(format: ConversionFormat) method to Connection, 'Node' and Graph. There is one ConversionFormat by conversion format. Each one implements a convert_graph(graph: Graph) -> str, convert_node(node: Node) -> str and convert_connection(connection: Connection) -> str. The convert method will then call format.convert_connection(self) (for a Connection here).

Should we implement a way for user to implement custom conversion ? If yes, this method won’t work, or each one should add their own ConversionFormat inherited class. Maybe they could customize a specific conversion format by inheriting from the specific inherited ConversionFormat (A user add a FooConversionFormat class which inherit from DotConversionFormat which inherit from ConversionFormat) ?

Don’t know if this is good to have to use custom classes for custom Node/Graph/Connection.

This would allow to load a graph from a file, and to save the graph to a file. Conversion format ideas: - dot (https://graphviz.org/doc/info/lang.html) - mermaid (https://mermaid.ai/open-source/intro/syntax-reference.html) - plantUML (https://plantuml.com) - RDF/XML (https://w3c.github.io/rdf-xml/spec/) - RDF/TURTLE (https://w3c.github.io/rdf-turtle/spec/) One possible strategy would be to implement those conversion is to implement a `convert(format: ConversionFormat)` method to `Connection`, 'Node' and `Graph`. There is one `ConversionFormat` by conversion format. Each one implements a `convert_graph(graph: Graph) -> str`, `convert_node(node: Node) -> str` and `convert_connection(connection: Connection) -> str`. The `convert` method will then call `format.convert_connection(self)` (for a `Connection` here). Should we implement a way for user to implement custom conversion ? If yes, this method won’t work, or each one should add their own ConversionFormat inherited class. Maybe they could customize a specific conversion format by inheriting from the specific inherited ConversionFormat (A user add a FooConversionFormat class which inherit from DotConversionFormat which inherit from ConversionFormat) ? Don’t know if this is good to have to use custom classes for custom Node/Graph/Connection.

linarphy added the

Importance/High

Kind/Feature

Complexity/Normal

labels

2026-06-06 22:02:09 +00:00

linarphy self-assigned this

2026-06-06 22:02:09 +00:00

linarphy added this to the Roadmap to 1.1.0 project

2026-06-06 22:02:12 +00:00

linarphy added a new dependency

2026-06-09 16:28:56 +00:00