-
Notifications
You must be signed in to change notification settings - Fork 357
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
Data-Table: Server-side paging and sorting #119
Comments
We are currently working on building smaller components like So basically we are gonna split the |
OK that sounds like a good seperation. Do you have a list what other things you are planning for the data table? I am asking because there are some tiny features missing which could be useful such as:
Let me know if I should create seperate feature request for those. |
Probably separate the We are trying to see what works best for this particular component. |
Btw, we are working together with one contributer (gistia) atm to allow template rendering in the data-table. So you will be able to add icons, buttons or w/e you want. |
Closing since it was addressed in #128. |
This repository's issues are reserved for feature requests and bug reports.
Feature Request
It should be possible to use server-side paging and sorting with the data table component.
What is the motivation / use case for changing the behavior?
Currently it is not possible to page and sort over large datasets as all data needs to be present in the client browser. I would have to load all records from my backend at once to the data table component.
Other information
Suggestion:
The developer could hook in his own backend calls and reload data from the backend based on page/sort events:
@output() sortChanged(already available)
@output() pagingChanged(missing)
The text was updated successfully, but these errors were encountered: