Explorer: day detail view #138

Closed
opened 2026-07-27 20:08:14 +00:00 by claude-bot · 1 comment
Contributor

Parent: #22. Second of the Explorer's three views.

A day detail page grouped by location, product family, severity, and event window, linking into individual event detail pages.

Tasks

  • Route and template for a single day.
  • Group by location, then product family; show severity and the event window.
  • Link each grouping through to its event detail page.
  • Bounded query — one day, reusing the calendar's aggregation shape.
  • Reuse visible_location_filter(user) from app/api/permissions.py.
  • Handle a day with activity at a location the user can no longer see, or that no longer exists — coordinate with the location-deletion issue.
Parent: #22. Second of the Explorer's three views. A day detail page grouped by location, product family, severity, and event window, linking into individual event detail pages. ## Tasks - [ ] Route and template for a single day. - [ ] Group by location, then product family; show severity and the event window. - [ ] Link each grouping through to its event detail page. - [ ] Bounded query — one day, reusing the calendar's aggregation shape. - [ ] Reuse `visible_location_filter(user)` from `app/api/permissions.py`. - [ ] Handle a day with activity at a location the user can no longer see, or that no longer exists — coordinate with the location-deletion issue.
Author
Contributor

Picking this up, stacked on the calendar page (#137, PR #170). Day route /explorer/{YYYY-MM-DD} grouped by location with severity/time-window per event and links through to the event detail page (#139, next); same local-day assignment rule, bounded ±2-day padded query reusing the calendar's aggregation shape, visible_location_filter throughout, archived locations shown with an "archived" badge (#134 coordination), SPC day-band risk chips per the #136 decision where cheaply derivable from the retained outlook pages.

Picking this up, stacked on the calendar page (#137, PR #170). Day route `/explorer/{YYYY-MM-DD}` grouped by location with severity/time-window per event and links through to the event detail page (#139, next); same local-day assignment rule, bounded ±2-day padded query reusing the calendar's aggregation shape, `visible_location_filter` throughout, archived locations shown with an "archived" badge (#134 coordination), SPC day-band risk chips per the #136 decision where cheaply derivable from the retained outlook pages.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/WeatherBot#138
No description provided.