feat(public-status): show active incidents and scheduled maintenance#227
Open
wispy92 wants to merge 1 commit into
Open
feat(public-status): show active incidents and scheduled maintenance#227wispy92 wants to merge 1 commit into
wispy92 wants to merge 1 commit into
Conversation
The public status page only rendered live component health, so there was no way to communicate ongoing incidents or planned maintenance to visitors. The `incidents` and `maintenance` collections are already publicly readable, so this is a frontend-only addition. - add publicStatusService to fetch active (non-resolved) incidents and scheduled/in-progress maintenance, scoped to the page and its services - expose them through usePublicStatusPageData - render IncidentsSection and MaintenanceSection banners above the current status card (hidden when there is nothing to show) - add i18n keys to the public namespace (type interface, en, km) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an Active Incidents banner and a Scheduled Maintenance banner to the public status page (
/public/:slug).Why
The public status page only reflected live component health computed from service checks. There was no way to communicate an ongoing incident or a planned maintenance to visitors, even though both already exist in the admin UI. This closes that gap so a status page can actually be used for incident communication.
How
publicStatusServicethat fetches active (non-resolved) incidents and scheduled / in-progress maintenance, scoped to the page (operational_status_id) and its services (service_id). Theincidentsandmaintenancecollections are already publicly readable, so no collection rule changes are needed.usePublicStatusPageData.IncidentsSectionandMaintenanceSectioncomponents rendered above the current-status card. Both render nothing when there is no active incident / maintenance, so existing pages are visually unchanged.publicnamespace (type interface,en,km).Testing
npx tsc --noEmit— passesnpx eslinton changed files — no new errorsnpx vite build— passesNotes