Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
feat(table): Emit event when local filtering changes number of result items - issue #650 #652
Addresses issue #650
When local filtering causes the number of pages to change, emits a
Can be used to re-set an associated
This PR includes documentation of the new event in
I could also add an event that emits the actual filtered item list (maybe a
Hmmm... That might kill 2 bids with one stone.
I was just thinking of a way to minimize the number of times events are fired. By checking if the page count has changed, then if items went from 14 to 13 (with page size of 5,), then the event wouldn't fire, because the page count hasn't changed, rather than emitting every time
But, it might just be simpler to set pagination with the "true" filter items length every time.
I'll tweak this tomorrow morning,.
Yep, there is support for server side pagination built into
If you are using item provider function you still need to provide pagination props to b-table to trigger a refresh of the items provider function.
But if you provide an reference to an array to items (not a function), then no need to tie pagination props to b-table, as updating the array will trigger b-table to redraw. You would just need to control the pagination element from your parent component or app.