Closed krlawrence closed 2 months ago
Here are some ideas of potential solutions:
I think I'm leaning toward option one. But to do paging well we will need to define a sort order for the queries so that when we load more pages we will get consistent results. Perhaps sorting by ID is the safest general approach since all nodes will have that attribute. However, if the ID is a UUID then sorting can be expensive.
Option 4 is also a solid choice. We'd have to build a proof of concept to see how to feels to use. As long as the app remains interactive while the progress is being shown and/or the action can be cancelled this could be a great option.
Community Note
Graph Explorer Version (and Graph Database and Version used if applicable) 1.6.0 Is your feature request related to a problem? Please describe. This is in many ways as much a bug as it is a feature request.
Double clicking on a node will cause its adjacent nodes and incident edges to be added to the canvas, but only if there are ten or less of them. This is a confusing user experience. To a user it feels more as if the double-click randomly works sometimes. The user experience here should be revisited.