Skip to content

Explore pups pagination fix#239

Open
qlpqlp wants to merge 3 commits into
Dogebox-WG:mainfrom
qlpqlp:explore-pups-pagination-fix
Open

Explore pups pagination fix#239
qlpqlp wants to merge 3 commits into
Dogebox-WG:mainfrom
qlpqlp:explore-pups-pagination-fix

Conversation

@qlpqlp

@qlpqlp qlpqlp commented Apr 17, 2026

Copy link
Copy Markdown
Contributor

No description provided.

qlpqlp added 2 commits April 16, 2026 19:08
Fixed pagination issue were wen going to page 2 it jumped to page 1
PaginationController now supports:
setFilter((item, query) => boolean) → set once
setQuery(query) → update often
internal applyFilter() to reuse the same predicate
clearFilter() helper
Backward compatibility is preserved: existing setFilter(fn) usage still works.
@qlpqlp

qlpqlp commented Apr 17, 2026

Copy link
Copy Markdown
Contributor Author

sorry I was using wrong branch

@elusiveshiba elusiveshiba left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes may have an unintended side effects, hiding changes if pup descriptions/logos etc. change without the ID being modified.

Seems to me the issue source is actually in src/components/common/paginator/paginator-controller.js's setData method.
It shouldn't have this.currentPage = 1; running every time setData is called.

Instead, it could just keep the current page, unless the total page count has reduced in which case it could just set the last page.

For eg.

const totalPages = this.getTotalPages();
this.currentPage = Math.min(this.currentPage, Math.max(totalPages, 1));

Also, does a fix need to be applied to the pup library page too?

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.

3 participants