-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Custom sort in table not working. #15550
Custom sort in table not working. #15550
Comments
Hi, https://primeng.org/table#removable-sort it works. Could you share stackblitz link? |
sortFunction is not triggered when lazy is true |
@Sinan997 I can confirm this is happening. Custom sort is not triggered if lazy load is being used. |
Fixed #15550 - Table | Custom sort in table not working
@mehmetcetin01140 @cetincakiroglu This was a breaking change, and doesn't make sense to me. As we have a shared wrapper where |
Describe the bug
Custom sort is not working expected. (sortFunction)="customSort($event)" is not getting triggered.Using the vesrion "primeng": "^17.16.0".
<p-table
#dt
[columns]="cols"
[value]="values"
(sortFunction)="customSort($event)" [customSort]="true"
[tableStyle]="{ 'min-width': '50rem' }"
[paginator]="true"
[rows]="10"
[scrollable]="true"
currentPageReportTemplate="Showing {first} to {last} of {totalRecords} entries"
(onPage)="onPaginate($event)"
[showCurrentPageReport]="true"
[totalRecords]="totalRecords"
[lazy]="true"
[rowsPerPageOptions]="[5, 10, 20]"
[selectionMode]="'multiple'"
[(selection)]="selectedRows"
In ts
import { ConfirmationService, SortEvent } from 'primeng/api';
customSort(event : SortEvent){
console.log(event);
}
tried as per the latest documentation.But customSort Method is not triggered while applying the sort.
Environment
local environment
Reproducer
No response
Angular version
17.00
PrimeNG version
17.16.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.11.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: