I think creating an agnostic of the app state component only has sense if this one is used in several contexts.
For example for a library of components as a table with advanced functionalities that will be used in several apps or a dropdown used in multiple places in your app.
But components (pages or not pages) used in a unique context I think that is not a problem.
Regards
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, thanks for your comment.
I think creating an agnostic of the app state component only has sense if this one is used in several contexts.
For example for a library of components as a table with advanced functionalities that will be used in several apps or a dropdown used in multiple places in your app.
But components (pages or not pages) used in a unique context I think that is not a problem.
Regards