refactor(ui): extract ConfigureSSOWizard and lift data ownership to the host#8799
refactor(ui): extract ConfigureSSOWizard and lift data ownership to the host#8799iagodahlem wants to merge 5 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Repository UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
🦋 Changeset detectedLatest commit: 168e840 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The standalone host content keeps its original ConfigureSSOContent name.
836b753 to
f7595ef
Compare
The
<OrganizationProfile />SSO surface is becoming a "Security" page that shows the connection state and launches the configuration wizard. This PR lays the structural foundation by separating the wizard (a pure flow) from its hosts (who own the data):ConfigureSSOWizard— the pure, data-injected ConfigureSSO flow: the provider seeded with host-supplied data plus the step graph, now assembled in one place. It performs no fetching and never observes a loading state; hosts own data fetching, the loading skeleton, and permission gating.OrganizationSecurityPagenow owns the data: it calls the enterprise-connection hook, gates loading and permissions, and injects the resolved data into the wizard. This is the seam the upcoming Security page overview builds on.ConfigureSSOcomponent (internal mount / sandbox) keeps owning its own data through its private content wrapper — the shape a future public standalone export would wrap.statussummary (unconfigured/in_progress/active/inactive): the display-facing lifecycle the Security page's badge/state model will read. The wizard's navigation guards keep reading the raw booleans.No behavior change on either mount; empty changeset.
Part of ORGS-1603. Stacked on #8796.