diff --git a/src/components/datatable/DataTable.vue b/src/components/datatable/DataTable.vue index 9f7f5b8df..5c65c33e3 100644 --- a/src/components/datatable/DataTable.vue +++ b/src/components/datatable/DataTable.vue @@ -1616,7 +1616,7 @@ export default { sortOrder: this.d_sortOrder, multiSortMeta: this.d_multiSortMeta, filters: this.filters, - filterMatchModes: filterMatchModes + filterMatchModes: filterMatchModes }; } }, diff --git a/src/views/datatable/DataTableDoc.vue b/src/views/datatable/DataTableDoc.vue index 6e69aa9f2..15a8ec2ae 100644 --- a/src/views/datatable/DataTableDoc.vue +++ b/src/views/datatable/DataTableDoc.vue @@ -713,7 +713,7 @@ export default { assuming there are actually records of totalRecords size although in reality they aren't as in lazy mode, only the records that are displayed on the current page exist.
Lazy loading is implemented by handling pagination and sorting using page and sort events by making a remote query using the information - passed to the events such as first offset, number of rows and sort field for ordering. Filtering is handled differently as filter elements are defined using templates. filter event is not triggered in + passed to the events such as first offset, number of rows and sort field for ordering. Filtering is handled differently as filter elements are defined using templates. filter event is not triggered in lazy mode instead use the event you prefer on your form elements such as input, change, blur to make a remote call by passing the filters property to update the displayed data. Note that, in lazy filtering, totalRecords should also be updated to align the data with the paginator.
@@ -1979,7 +1979,7 @@ export default { event.sortOrder: Sort order as integer