Current q-data-table implementation requires all rows to be given to the component, what if the data too large (500k+) for the phone or for the server to query/deliver? It would be nice if there's a handler that triggered every sort, goto-page or change-page-size event:
order, page, rowsPerPage, updateCallback), where:order is the column order, something like: ["+foo","-bar"] or [{asc:true,key:"foo"},{asc:false,key:"bar"}] for multicolumn sorting, page is the page requested (1..ceil(data.length/rowsPerPage)), rowsPerPage is the paging size, updateCallback is the function that update function, that requires 4 arguments:rows, for updating/replacing data propertycurrentPage, for case when user trying to go to page that not existstotalRows, for calculating last page rowsPerPage, for case when user trying to send improper rowsPerPage, updating the options.pagination.rowsPerPageNICE!
This is the most important missing feature for us.
This is a feature, that if not implemented, would force us to move away from quasar as a framework, because it's key in almost every application we make/will make.
@Hoagiex Hi, couple of things:
Please contact me by email ([email protected]) or even better by Gitter to discuss on your company's needs. Thanks!
@Hoagiex... Be quasar patreon and help him grow! Questioning is easy, I want to see ...
any update?
Hi,
Have you added this feature to v0.14 ?
This will go to v0.15. It's getting there. DataTable revamp is 95% done.
Closing as code is ready in future v0.15 datatable revamp.
@rstoenescu What the time to publish v0.15? It seems v0.15 has a lot of nice features that I can鈥檛 wait for it!
Hi @luozhihua , Doing my best to release it this month.
馃憤 Really looking forward to
Most helpful comment
@Hoagiex Hi, couple of things:
Please contact me by email ([email protected]) or even better by Gitter to discuss on your company's needs. Thanks!