Pagination and Pagination Info
Pagination and pagination info are still in the package but no longer part of
vuetable. That means you will have to explicitly include them in your template and wire them up to
vuetableusing availble events.
This is very easy though. Basically, you just need to listen to
vuetable:pagination-dataevent to get the pagination information, then call
PaginationInfocomponents. Please see the provided example.
The reason behind this is that uncoupling the pagination and pagination info components from
vuetablemakes it more flexible and light weight. If you do not need pagination component, you don't have to use it. Or if you want to use your own pagination component or put it somewhere else, you can easily do that.
Due to the change in Vue 2.0 the deprecates
$dispatchthe events and encourages the use of centralized event hub, you can no longer send an event to
vuetableto perform the task (e.g.
vuetable:refresh) as before.
In earlier version of
vuetable, it usually uses and provides those events for communications between its internal components (e.g. Vuetable, VuetablePagination, etc). In this case, moving all those events to
vuexseems over-kill and inappropriate since
vuexis intended to be use as an centralized state management for an application.
Although, those events were removed in this version, but almost all the functionality are still there in the methods inside
vuetable. You can easily call it by referencing
vuetablecomponent in your code using
For the list of availble and removed events, please see the [What's Change] section.
__actionsspecial field was deprecated and can easily be replaced by the
__componentspecial field, which is more useful and shouldn't have any limitation since you can now use the full power of Vue.js.
Please see the provided example for the replacing action component.
The type of
append-paramshas been changed from
All the related CSS classes has been moved into
cssprop, which is an
Objecttype. This should make the template shorter and cleaner to look.