You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our frontend separates the idea of a regular network (think hairball type) from a bipartite or other network. This is not ideal. It would be more helpful to have a single Network component that could handle all the cases.
A little background:
Originally we started abstracting away from a Network component becuase it seemed like it would end up just being visx's Graph component.
We're realizing now that our component would differ a bit from the visx Graph. It would have default layouts and node interactions.
We're realizing we want all of our networks across the site to look and feel the same. That goal will be much more easily managed if we have only one Network component.
Network would be very similar to BipartiteNetwork but would be more general. For starters,
The data prop should be "exploded" to be the props nodes, links, and partitions, the last being optional
The type of the partitions prop should be { name?: string, nodeList: string[]; }
If partitions is empty, then a simple graph will be rendered
( from Dave in slack)
Network should have a default layout if node x and y values are not provided. For the case where the graph is partitioned, the default layout would be nodes aligned in columns according to their partitions. For the case of no partitions, the default should be a ring.
The text was updated successfully, but these errors were encountered:
Dependency of #924 and #1038
Currently our frontend separates the idea of a regular network (think hairball type) from a bipartite or other network. This is not ideal. It would be more helpful to have a single
Network
component that could handle all the cases.A little background:
Network
component becuase it seemed like it would end up just being visx'sGraph
component.Graph
. It would have default layouts and node interactions.Network
component.Network
would be very similar toBipartiteNetwork
but would be more general. For starters,( from Dave in slack)
Network
should have a default layout if node x and y values are not provided. For the case where the graph is partitioned, the default layout would be nodes aligned in columns according to their partitions. For the case of no partitions, the default should be a ring.The text was updated successfully, but these errors were encountered: