-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pagination handling example #241
Comments
Pagination is handled externally: <Data as |d|>
<YourTable @data={{d.records}} />
<Pagination @meta={{d.meta}} @onNext={{d.nextPage}} />
</Data> records would be tracked, no when the pagination component tells the data component to update, the table component updates because of auto tracking The pagination interface in this repo was accidentally left in, and isn't actually used, afaik |
Thanks in the example above, how can I tell the table that I changed the @DaTa (without triggering a new route)? |
Why don't you want to trigger a route transition? Generally folks want table state serialized to the URL |
Because I have several tables inside my page and I want to be able to paginate each one indipendently |
If you move all data loading for each table into component-land instead of the route, your goal is very doable |
yes that's my goal, but how do I trigger a table redraw after pressing the pagination buttons? |
In the example, if records is I can share a real/runnable example later if you're still stuck |
Everything works as expected, thanks! |
In the class list I found something related to pagination but I can't find any example using it so I'm unable to understand how to use it
The text was updated successfully, but these errors were encountered: