For that, you can manage the state locally in your component too with a local stateful service that is tied to the providers of the component. You don't have to use a centralized store for that, it creates a whole category of issues where the state needs to be cleaned up once you navigate away. It's much better to have the state cleaned up automatically when the component that loads the paginated data gets destroyed.

Pipes are designed mostly for synchronous transformation of data in the template, like converting a string to a date. If you want to transform the data coming from the backend, you can do that directly on the service itself, or on the component if the output of the transformation is specific to a component, but a pipe is not the recommended way of doing that. 👍

@@AngularUniversity Thank you for your advice, it helps me a lot. May I ask another question? In Angular 17, how can we define a global service, pipe, etc.. that all components can use it without import for each one (in Angular 17 they remove app.module.ts so I don't know how to do it).

@@phuoctoanchauhuynh8557 Sure, use @Injectable({providedIn: 'root'}) on top of the service class, and the service will be injectable anywhere on the application: components, pipes, directives, etc.