Repository navigation
test(web): reproduce overlapping newest-first message pages - #4719
Subham-KRLX wants to merge 1 commit into
Conversation
Document the final partial page overlap reported in apache#4717 with a skipped regression test and passing initial-page controls. Keep the implementation pending agreement on the issue. Pass the query through resolve so the existing navigation passes lint without changing its destination.
|
Thanks for the PR. It is labeled If AI was used to create this PR, you must run the Slash commands (own line, regular comment) move it around the queue:
See CONTRIBUTING.md for details. |
|
@Subham-KRLX ,I reproduced #4717 locally and ran the regression test. This test reproduces the same overlap I observed in the UI. Given the staged migration to Dioxus planned in #4633 , could you check with the maintainers whether this issue should be fixed in the current UI? Please proceed based on their guidance |
|
lets merge this after #4644 (and all subsequent PRs leading to dioxus-based web-ui), maybe this bug doesnt exist there. |
|
/author |
|
I will hold off on the fix until the Dioxus migration lands then recheck pagination in the new UI and proceed based on maintainer guidance. |
Which issue does this PR address?
Relates to #4717
Rationale
Newest-first pagination repeats 15 messages on the final page when a partition contains 25 messages.
What changed?
A regression test documents the overlap with passing controls for initial pages in both directions. The failing case is skipped pending agreement on the fix, following the contribution guidelines. The navigation query now passes through
resolve()to satisfy lint without changing the destination.Local Execution
prekhooks passed.