Skip to content

WIP: Add user-friendly sort order to initial pages in collection replay.json endpoint#3362

Draft
tw4l wants to merge 2 commits into
mainfrom
issue-3356-coll-replay-page-sort-order
Draft

WIP: Add user-friendly sort order to initial pages in collection replay.json endpoint#3362
tw4l wants to merge 2 commits into
mainfrom
issue-3356-coll-replay-page-sort-order

Conversation

@tw4l
Copy link
Copy Markdown
Member

@tw4l tw4l commented Jun 5, 2026

Fixes #3356

This PR applies a new sort order to the initialPages returned by the collection replay.json endpoint, as part of the solution to provide a more sensible order of pages in collection replay.

Specifically, this applies isSeed as the primary sort order, followed by url and then ts.

Kept in draft for now for two reasons:

  • It appears RWP/wabac.js is adding its own sort order for pages regardless of what the backend passes in, so this change alone doesn't resolve the problem
  • I'm unsure at this point if adding the query parameters to the pagesQueryUrl to match the initialPages sort order will break any of the code in RWP/wabac.js that fetches subsequent pages

tw4l added 2 commits June 5, 2026 13:44
The initial pages loaded for collection replay are not currently
sorted except in the order they come out of the database. This
commit applies a sort order of isSeed, with secondary and tertiary
sorts by url and timestamp. The same sort and sort order are also
added to the pagesQueryUrl for the same endpoint, which may require
changes in ReplayWeb.page or wabac.js to be able to handle.
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.

[Task]: Add secondary sort for collection pages in Replay UI

1 participant