PrimeNG p-table and HttpClientTestingModule: Pagination State on Empty Datasets

Integration of PrimeNG Table with Mocked HTTP Services

When integrating the p-table component with Angular's HttpClientTestingModule, developers typically use the [lazy] input to trigger data fetching via the onLazyLoad event. This allows the UI to be tested against mock observables without requiring production credentials or a live backend.

A specific challenge arises when verifying the table's behavior during edge cases, such as when a mocked service returns an empty dataset. In PrimeNG versions 13.x and later, the table's internal pagination state may not automatically reset when the returned data length is zero, potentially leading to discrepancies between the current page index and the actual available data.

This creates uncertainty when writing assertions for empty states, as the component may maintain a page index that no longer corresponds to any existing records.

• Does the p-table component provide a built-in mechanism to reset pagination state when a lazy-loaded request returns an empty array?
• Is there a recommended configuration to ensure the page index synchronizes with the dataset length during mock-driven integration tests?