p-table: custom sort should not be invoked if lazy is true

[MikeMatusz]

Describe the bug

If I configuring the p-table for lazy-loading, the sort should be handled on the server or in the onLazyLoad function, otherwise the sort has only a portion of the total data source available. And if we are already sorting on the server, it tries to run additional client-side logic to sort, which may conflict.

Numerous issues have come up in the past about using them together, and the response has always been the same as above. That changed suddenly with #15550 and caused issues we had to work around in our code. This was a breaking change, not a fix, and I'm not sure the utility of it.

If new records are returned when you load the next page, the client-side sort might interleave them with the first set of results, which would be a very confusing user experience. I can't think of a good use case for supporting this, as it seems like it could only cause undesirable behavior.

Environment

N/A

Reproducer

No response

Angular version

17

PrimeNG version

17

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

[mertsincan]

Could you please try the latest version?

[github-actions]

We're unable to replicate your issue, if you are able to create a reproducer by using PrimeNG Issue Template or add details please edit this issue. This issue will be closed if no activities in 20 days.

[MikeMatusz]

I cannot replicate the issue in the latest version. Looking at the code I believe this was fixed by #16235.