I have a collection that returns several records. Within each record, there is a related list of records. I’m displaying these related records in a table. Sometimes the list of related records can be large enough that it makes the UX unwieldly, so I’d like to be able to paginate this related list. But the default paginator only works on the base collection.
you should be able to use the custom mode of the paginator. Although this would only paginate the data on the front end. If you want to do it on the backend and are using superbase you can do this with a select, or a backend function
Paginating on the front end is all I need as it’s only a UX issue.
Maybe I just don’t know how to use the paginator in custom mode… thought that was a backend implementation.
My workaround was to dynamically create some buttons based on list size (1-10, 11-20, 21-30, etc) and bind them with an on-click action to some logic on the filtering of the list data. Works pretty good, just took an hour to setup.
I think you could just create a new collection that is filtered by the main collections id and then backend paginate that new collection. Link the related table to that new collection and then I think you would have to use the item id of the main collection list so it chooses the correct table data.
Does that make sense? Im not in front of weweb right now but in my head that would work.