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

Make browser history know about pagination #1742

Merged
merged 22 commits into from
Mar 1, 2024

Conversation

swistak35
Copy link
Contributor

No description provided.

@swistak35 swistak35 force-pushed the rl-browser-pagination-history branch from a997c6b to 1e3e8b7 Compare February 11, 2024 15:51
@swistak35 swistak35 force-pushed the rl-browser-pagination-history branch from 649c2ef to cf8a0ab Compare March 1, 2024 08:22
@swistak35
Copy link
Contributor Author

A few more design (as in: code) improvements could be made:

  • Pagination.Specification could have another similar component, but knowing also what resource is being paginated, so that full specification can be passed over to Api, for example
  • Pagination buttons could be extracted to separate component with it's own model?

I have a thought that instead of decomposing the model/flags and passing down only subset of fields, it would be better in most cases to pass whole model/flags, and decompose only if we are really on the bottom of displaying something. For example, I needed to pass down much more data into displayPagination, because there was assumption, that only links are enough, but it isn't. To that point it would still be good to pass everything from current component.

@swistak35 swistak35 merged commit 35606a7 into master Mar 1, 2024
46 checks passed
@swistak35 swistak35 deleted the rl-browser-pagination-history branch March 1, 2024 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant