Currently if you have a raphtory graph with edge properties and map it to a networkx graph, the properties are in a new map with keys "constant" or "temporal". Upon selecting temporal, the value of each is returned as a list of k,v tuples rather than a dict which makes accessing the value of one property a bit clunky, e.g. if you call g.edges.data("temporal") it might look like this for one edge.
Even better, I believe the old version of to_networkx (when it was in python before rust), when you set explode_edges to true would return multiple edges each with just one flat property with that name, so that upon calling g.edges.data("boolean_prop") it would return something like
('node_a', 'node_b', (1465088400000, True))
since each exploded edge has just one temporal property update. Would it be possible to have something like this again?
Currently if you have a raphtory graph with edge properties and map it to a networkx graph, the properties are in a new map with keys "constant" or "temporal". Upon selecting temporal, the value of each is returned as a list of k,v tuples rather than a dict which makes accessing the value of one property a bit clunky, e.g. if you call
g.edges.data("temporal")
it might look like this for one edge.Could this be changed to be a dict? I.e.
Even better, I believe the old version of to_networkx (when it was in python before rust), when you set
explode_edges
to true would return multiple edges each with just one flat property with that name, so that upon callingg.edges.data("boolean_prop")
it would return something likesince each exploded edge has just one temporal property update. Would it be possible to have something like this again?
Happy to expand or help make the fix :)