Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0); details open in place, loading hourglass (0.143.0); attendee and resource fix… #104
No reviewers
Labels
No labels
audit
bug
cleanup
docs
duplicate
enhancement
help wanted
invalid
new feature
P0
P1
P2
P3
question
roadmap
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
pyaniz/Thursday!104
Loading…
Reference in a new issue
No description provided.
Delete branch "staging"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Three features and a fix on
staging(0.141.0, 0.142.0, 0.143.0, then 0.143.1).0.141.0: dashboard polish
0.142.0: one Edit Session window, with expansions
features/sessions/SessionEditDialog.tsx) used by both pages.calendar_event_expansions(migration V65), keyed by event id like game overrides and session resources, so it covers planned sessions and Google events. NewPUT /calendar/events/{id}/expansions; calendar events carry anexpansionslist. Deleting a planned session removes its expansions.0.143.0: details in place, and a loading hourglass
GET /games/{id}returns one game in the Collection's shape (plays, votes, owners, tags) for any game that has been played, not only collection games; group access is checked as for other group data.LoadingHourglasscomponent.0.143.1: fixes in Edit Session
PUT /calendar/events/{id}/attendees, existingsession_attendeestable, no migration) and shown with the Google guests. Stored attendees were also saved as "going", which the Dashboard does not group by, so they never showed there; they are now read as accepted / tentative / declined.0.143.2: dialog stacking
Verified
tsc -bandnpm run buildpass; the edited backend files compile.GET /games/{id}queries were run on Postgres 17 against a small copy of the tables.test_session_expansions.py,test_game_detail.py,test_event_attendees.py) pass with a stand-in runner (pytest is not installed here): please runpython -m pytestinbackend.Not verified
To test on staging
Dashboard: click the pencil on the next session and on an upcoming one: the Edit Session window opens. Change the game, save, and see it on the card.
Pick a game with expansions, tap two, save: "+ A, B" shows on the Dashboard card and in the Planner timeline. Reopen the window: they are still selected. Change the game: none selected.
Planner: open, edit and delete a session as before; attendees and resources still work.
Dashboard winner card colour with a few winners, 9 recent plays.
Click both Most Played games: the details dialog opens on the Dashboard after a brief hourglass; vote buttons and tabs work. Try a game nobody owns.
Open the Collection: hourglass, then the list fades in; vote on a game and check the list does not flash.
Edit Session on a Google Calendar session: add an attendee on Details, save, reopen: still there, and shown on the Dashboard card. Same on a session created in Thursday.
Manage Resources: "All game resources" opens the Collection's game dialog on Resources, in front. From inside it open the resource editor (and a dropdown in it), and pack-away if you use it: each opens above the previous one.
Release notes added for all versions.
🤖 Generated with Claude Code
Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0)to Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0)- The Edit Session dialog moves out of the planner into features/sessions/SessionEditDialog.tsx; the planner and the dashboard both use it. The dashboard's pencil no longer opens the Override Game box. - Expansions can be chosen on the Game tab (ExpansionSelector) and are shown under the game in the planner timeline and on the dashboard cards. - Migration V65: calendar_event_expansions, keyed by event id. New PUT /calendar/events/{id}/expansions; calendar events carry `expansions`; deleting a planned session removes its expansions. - Tests: test_session_expansions.py. Docs and the planner help page updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0)to Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0); details open in place, loading hourglass (0.143.0)- New GET /games/{id}: one game in the shape of a Collection entry (plays, votes, owners, expansions-based player count, tags) for any game, seen from the caller and, with group_id, from that group (read access is checked). - The dashboard opens GameDetailsDialog in place with a Backdrop hourglass while the game loads; the router-state hop to /collection is removed. - Collection: first load and group change show a LoadingHourglass and the list fades in; refreshes keep the list on screen. Honors reduced motion. - Tests: test_game_detail.py. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0); details open in place, loading hourglass (0.143.0)to Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0); details open in place, loading hourglass (0.143.0); attendee and resource fix…- Attendees added on a Google Calendar session were dropped on save. They are now stored via PUT /calendar/events/{id}/attendees (session_attendees, no migration) and returned with extra=true next to the Google guests. - Stored attendees were saved as "going", which the dashboard does not group by, so they never showed there. They are now read as accepted / tentative / declined. - Manage Resources: "All game resources" opens GameDetailsDialog on its Resources tab (as in the Collection) instead of the old separate editor. - Tests: test_event_attendees.py. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0); details open in place, loading hourglass (0.143.0); attendee and resource fix…to Feature: dashboard most played games open their details, winner card uses the opposite colour, nine recent plays (0.141.0); one Edit Session window with expansions (0.142.0); details open in place, loading hourglass (0.143.0); attendee and resource fix…