Skip to content
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

Table> double call to (onLazyLoad) event after #15996 #16070

Labels
LTS-FIXED-15.4.25 LTS-FIXED-16.9.14 LTS-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working v18-port
Milestone

Comments

@ymg2006
Copy link
Contributor

ymg2006 commented Jul 21, 2024

Describe the bug

When lazy is true on the table sorting causes double call to (onLazyLoad) event after commit: Fixed #15550 - Table | Custom sort in table not working #15996.
Screenshot 2024-07-21 093654

Environment

Windows 11

Reproducer

No response

Angular version

17.3.6

PrimeNG version

17.18.5

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

v20.12.1

Browser(s)

All

Steps to reproduce the behavior

<p-table #dataTable
(onLazyLoad)="getUsers($event)"
[value]="users"
[rows]="100"
[lazy]="true"

Expected behavior

one call to onLazyLoad.

@ymg2006 ymg2006 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jul 21, 2024
ymg2006 pushed a commit to ymg2006/primeng that referenced this issue Jul 30, 2024
@cetincakiroglu cetincakiroglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Aug 1, 2024
@cetincakiroglu cetincakiroglu added this to the 17.18.7 milestone Aug 1, 2024
cetincakiroglu added a commit that referenced this issue Aug 1, 2024
closes #16070 Table> double call to (onLazyLoad) event
@sparmar-agilic
Copy link

Is this issue fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment