supabase / supabase / 42020104445

87%

push

github

feat(studio): update flags for interstitals and apps list (#52955)

## Problem

The single `OauthAppScopedGrants` flag gates three independent areas of
scoped OAuth apps, so they can't be rolled out or rolled back
separately.

Resolves FE-4919

## Solution

Replace `OauthAppScopedGrants` with three flags, one per concern, and
remove the old one. Gating is a straight swap with no behavior changes.

| Flag | Files |
| --- | --- |
| `enableScopedOAuthConsent` | `pages/authorize.tsx` |
| `enableScopedOAuthPublish` | `PublishAppSidePanel/index.tsx` |
| `enableScopedOAuthManage` | `OAuthApps.tsx`, `pages/account/apps.tsx`,
`AccountLayout.tsx` |

The `authorize` page test now mocks only the consent flag.

Note: `PublishableApps` (the org apps list) isn't gated today, so Manage
covers only the authorized-apps table and the account page. I left that
as is to keep this a pure flag swap.

## Review instructions

Each flag can be toggled on its own.

1. Consent only: `/authorize?mock_scenario=default` shows the new
consent screen. The app form and list pages are unchanged.
2. Publish only: `/org/[slug]/apps`, then publish or edit an app. The
extra controls appear and nothing else changes.
3. Manage only: `/org/[slug]/apps` shows the new authorized-apps table,
and `/account/apps` renders. `/authorize` uses the legacy screen.
4. All off: behavior matches `master`.

Before merging, the three new flags must exist in ConfigCat with the
same targeting that `OauthAppScopedGrants` has today.

2043 of 2411 branches covered (84.74%)

Branch coverage included in aggregate %.

2839 of 3198 relevant lines covered (88.77%)

198.7 hits per line