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
Is your feature request related to a problem? Please describe.
I am working on a project where we allow users to create collections of products. For this reason, we hope for a ton of collections to be made. For organizational purposes, all of these collections will have the same parent. The problem is, the Admin UI will load 999 child collections when you expand the "folder" of a parent collection, and it will load those all at once. I fear that opening the parent folder for our user-generated collections will cause a query that takes forever and has a giant response, and still might leave us unable to load all of our collections.
Describe the solution you'd like
Instead, I think the Admin UI should load in a fixed number of child collections at a time: say, 50. Then, there should be a button below these collections to "Load More", and that should load in the next 50 collections. This should be able to continue as long as there are more collections to load.
Describe alternatives you've considered
An alternative would be to properly paginate the child collections. However, this would require much weirder UI (since each root-level collection with a lot of children would have its own pagination controls). So, overall, I'm unsure as to how this could be implemented more smoothly.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am working on a project where we allow users to create collections of products. For this reason, we hope for a ton of collections to be made. For organizational purposes, all of these collections will have the same parent. The problem is, the Admin UI will load 999 child collections when you expand the "folder" of a parent collection, and it will load those all at once. I fear that opening the parent folder for our user-generated collections will cause a query that takes forever and has a giant response, and still might leave us unable to load all of our collections.
Describe the solution you'd like
Instead, I think the Admin UI should load in a fixed number of child collections at a time: say, 50. Then, there should be a button below these collections to "Load More", and that should load in the next 50 collections. This should be able to continue as long as there are more collections to load.
Describe alternatives you've considered
An alternative would be to properly paginate the child collections. However, this would require much weirder UI (since each root-level collection with a lot of children would have its own pagination controls). So, overall, I'm unsure as to how this could be implemented more smoothly.
The text was updated successfully, but these errors were encountered: