Skip to content

fix(schedule): break headline location reads venue, not first audience room#290

Merged
JacobCoffee merged 1 commit intomainfrom
break-display-room
May 1, 2026
Merged

fix(schedule): break headline location reads venue, not first audience room#290
JacobCoffee merged 1 commit intomainfrom
break-display-room

Conversation

@JacobCoffee
Copy link
Copy Markdown
Member

Summary

Friday morning Break headline showed "Room 201B" and Saturday morning Break showed "Room 103ABC" because the schedule timeline picks the first room from the comma-joined fan-out. Coffee/snacks are actually in the Expo Hall AB. The DB-side fix already labels the slot `Break (Expo Hall AB)`; this PR pulls that parenthesized venue out for the headline.

How

  • Added a `displayLocationOverride` per-session string. For `kind=break` slots, parses the trailing `(...)` from the slot name (with the same `Hall …` → `Expo Hall …` normalization the plenary path uses) and stores it.
  • After room fanout, `displayLocation` prefers the override when present, else falls back to the first room as before.
  • `session.location` (the comma-joined fanout source) is unchanged, so the break still appears in every audience room's room-detail.

Test plan

  • Friday timeline 10:30am Break: headline reads "Expo Hall AB", not "Room 201B".
  • Saturday timeline 10:05am Break: headline reads "Expo Hall AB", not "Room 103ABC".
  • Each audience room (Grand Ballroom A, 103ABC, 104AB, 201B, etc.) still has the Break entry in its room-detail view.
  • Sat afternoon Break (15:45-16:15) still shows whatever room it's labeled with (or first audience room if untagged).

🤖 Generated with Claude Code

…e room

A "Break" slot fans out to every audience room (Grand Ballrooms,
103ABC, 104AB, 201B, etc.) so attendees in each room see "break time"
in their room-detail view. But the schedule-timeline headline was
using the first room from that fan-out list — which gave us things
like "Break · Room 201B" or "Break · Room 103ABC" when coffee/snacks
are actually in the Expo Hall AB.

The DB-side fix already lands the venue in the slot's content_override
(e.g. "Break (Expo Hall AB)"). This pulls that parenthesized suffix
out for break slots and stuffs it into a new
displayLocationOverride that wins over the audience-room first-pick
when computing displayLocation. session.location (the comma-joined
fanout source) is left untouched so per-room visibility is unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@JacobCoffee JacobCoffee merged commit baf48a5 into main May 1, 2026
2 checks passed
@JacobCoffee JacobCoffee deleted the break-display-room branch May 1, 2026 14:30
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