[drhayes9]

What does it do when there's 10k items? Is there a search or are you scrolling through all of them to find what you want? Is each expansion a network request to get the fields of the child?

I've been thinking a lot about how to solve this and I don't really have any answers. Curious if you're doing something different.

[alexwolfe]

Currently Vulcan just displays a long list which is not ideal. However in the Firebase Dashboard we do implement a solution for this. The approach I took there was to truncate the list at 1000 items and display something like [3,332 more items...] as the last node. When you click on the last node it displays another 1000 items, etc. Adding search to the existing implementation would be ideal.

When you open a node there is not network request, there is an open socket connection that data passes through.

Its usually not necessary to display all items in a 10k plus list as there is generally no use case for a user scrolling through a list that large. Search and showing a truncated list that renders efficiently would be a good approach. Ultimately the problem we are tying to solve is helping a user find the data they are looking for. hope that helps.

[drhayes9]

It does, yeah! Thanks for letting me pester you.