Skip to content

Activity page rework with paged runs and replay buttons - #8

Merged
github-actions[bot] merged 14 commits into
sourcejump:u/zasbufrom
zasbu:feat/activity-rework
Nov 6, 2026
Merged

github-actions[bot] merged 14 commits into
sourcejump:u/zasbufrom
zasbu:feat/activity-rework

Conversation

@zasbu

@zasbu zasbu commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Reworks the Activity page into one board: the runs chart on top, then the filters, then the runs table.

  • Each run's time shows its gap to the record in brackets, with how long ago it was set underneath. The When column is gone.
  • A play button on each row opens the replay in a dialog. Middle, ctrl or right click opens the run page in a new tab. It shows on every run because the recent runs API doesn't say which runs have a replay.
  • The table is paged (15 rows) instead of "Show more". Runs load 100 at a time and are paged in the browser, so turning a page is instant, and the next batch loads in the background. The page is kept in the address (?page=).
  • The pager has first/next/previous links, the current page and its neighbours, and a Go to box. It's shared with the Maps list, which now also shows its total.
  • The filter buttons and their dropdowns have a cleaner look, also shared with the other pages that use them.
  • The narrower page width is now available as Page width="medium".

Builds on #3 to #7, so their changes show in this diff too.

Replays in the dialog can't load map files on previews or localhost yet. files.sourcejump.net only allows https://beta.sourcejump.net in its CORS settings.

@github-actions
github-actions Bot changed the base branch from main to u/zasbu November 6, 2026 14:57
ddyfad pushed a commit that referenced this pull request Nov 6, 2026
External audit, 2026-11-06 (#4, #5, #7, #8 and #14).

- Active bans are two views (migration 0047): `active_bans`, and
  `records_bans` for the ones that keep a player off the boards. The 13
  copies of the condition read them. Views, so the planner still runs a
  board's ban check as one anti-join.
- WR history, recent runs, the Discord feeds and the daily totals read the
  stored `runs.was_record` instead of working it out again. The Discord
  WR feed took any rank-1 run, so it announced ties as world records.
- Standings break ties on the SteamID, so offset pages keep one order. The
  web table drops repeats and stops at an empty page.
- A timed records ban ends with nothing written, so a job looks every five
  minutes for players it should put back on the Pre-2.0 standings.
- Daily totals recount older days that late, invalidated or restored runs
  changed, which a trigger on runs records (migration 0048).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

Couldn't merge into u/zasbu, most likely because of a conflict. Update your branch from u/zasbu and push again.

@github-actions
github-actions Bot merged commit a1b54eb into sourcejump:u/zasbu Nov 6, 2026
3 checks passed
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

Merged into u/zasbu. It'll be live at https://zasbu-sj.okwhiteli.st in a few minutes.

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