Integrate Maintenance and Impending Messages Into ui-core Cellix Package - #333
Open
aaron-rabinowitz wants to merge 1 commit into
Conversation
Contributor
Reviewer's GuideThe PR extracts feature-flag loading and maintenance scheduling/presentation into the reusable @cellix/ui-core package, with explicit runtime and display contracts, while preserving OCOM-specific Apollo/OIDC/logout behavior in a thin ui-shared adapter and updating both applications and route layouts to use the new API. Sequence diagram for maintenance status and kickout flowsequenceDiagram
participant App as OCOM application
participant Adapter as OcomMaintenanceMessageProvider
participant Core as MaintenanceMessageProvider
participant Flags as FeatureFlagProvider
participant Clock as Server clock
participant Auth as OIDC and Apollo logout
App->>Adapter: render portalKey and timeoutBeforeMaintenance
Adapter->>Core: render with runtime
Core->>Flags: useFeatureFlags()
loop every 5 seconds
Core->>Clock: getServerDate()
Clock-->>Core: server timestamp
Core->>Core: update isImpending or isMaintenance
end
Core-->>App: render maintenance state and messages
loop every second while approaching
Core->>Core: decrement countdown
end
Core->>Adapter: onMaintenanceKickout()
Adapter->>Auth: HandleLogout()
Adapter->>App: navigate('/')
Flow diagram for OCOM application maintenance renderingflowchart TD
Community[ui-community App] --> CommunityProvider[OcomMaintenanceMessageProvider community]
Staff[ui-staff App] --> StaffProvider[OcomMaintenanceMessageProvider staff]
CommunityProvider --> CommunityState[useMaintenanceMessage]
StaffProvider --> StaffState[useMaintenanceMessage]
CommunityState --> CommunityLayouts[Community route layouts]
StaffState --> StaffLayouts[Staff route layout]
CommunityLayouts --> CommunityMessage[Portal-specific maintenance or impending message]
StaffLayouts --> StaffMessage[Portal-specific maintenance or impending message]
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
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.
Summary by Sourcery
Move feature-flag and maintenance messaging into the reusable Cellix UI core package and adapt OCOM applications to provide portal-specific runtime integration.
New Features:
Enhancements:
Build:
Documentation:
Tests:
Chores: