Make the client render node types, etc. on large networks #215
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Does this PR close any open issues?
No
Give a longer description of what this PR addresses and why it's needed
The client was hitting a limit in python-arango when trying to use the multinetjs functions
api.nodesandapi.edges. The code for that triggers aUNIONin the API, which blows up memory usage. To get around those limitations, I switched the API routes used here to use ones that don't require aUNION.I think that the solution for the
nodespanel in the bottom right is ugly and we could do something else. I wasn't sure what to do, so I left that for discussion.Provide pictures/videos of the behavior before and after these changes (optional)
Old:

New:

Are there any additional TODOs before this PR is ready to go?
TODOs: