A component with one param (a collection) displays the elements of the collection. This is done by binding the container with the passed collection. The pagination element inside should also be bound to the passed collection but it seems unbindable.
In the screenshots below we are in the component. The container is bindable to the passed collection and the paginator isn’t.
Yep, I raised this issue a long time ago (December 2023) - still hasn’t been tackled, it’s not only about a few things, but many things aren’t bindable yet unfortunately.
@broberto thanks for sharing your experience. Too bad because I find reusability in weweb generally quite good. Maybe an oversight.
Still other than passing params and having the collection formed inside of the component, I’m curious what other workaround patterns the community has explored…
I went digging a little bit, and if you wanted to do this, you can and it’s actually pretty simple.
What you want to do is the following:
Create your component, with your paginator, it has to be set to Custom Pagination
Create a variable of type Collection (collection_id) on that component
Add an On change event onto your pagination element, by using the details from the event, you can use this method in a Custom JavaScript Action (this method is what WeWeb uses to do the same with the paginator):
wwLib.wwCollection.setOffset([your_colleciton_id_variable_here], [event.index] * [event.offset]);
// This wwLib method takes two arguments, setOffset(collection_id <uuid>, offset <integer> )
The offset is basically how many items you want to have, so lets say you want to have three items per page, for a page two, this would be six items (2*3). I’ve tested it and it actually works.