supabase / supabase / 41857283487

87%

push

github

refactor(studio): align OAuth role validation failure types with the API (#52532)

## Problem

The scoped OAuth consent screen is still mock-backed, and its types for
`role_validation_failed` responses don't match what the platform API
will return. The API reports only the role level (`owner`,
`administrator`, `developer`, `read-only` or `no-access`) in each
failure, not the full role object, and project failures carry no `name`.

## Solution

- `OAuthScopeValidationResult` uses `{ name: 'owner' | 'administrator' |
'developer' | 'read-only' | 'no-access' }` for `role` in all three
`scope_target` variants, and project failures drop `name`.
- The mock approval and preflight responses build that shape from the
mock org roles.
- `types.test.ts` fixtures follow the new shape.

The consent screen only reads `ref` from project failures, so there is
no UI change.

The types are hand-written until the API change that introduces this
shape lands and `api-types` is regenerated.

Verification: `vitest run data/oauth-apps
components/interfaces/Organization/OAuthApps` (115 passed). `tsc
--noEmit` reports one error in `packages/ui-patterns`, which also occurs
without this change.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>

1991 of 2360 branches covered (84.36%)

Branch coverage included in aggregate %.

2806 of 3164 relevant lines covered (88.69%)

197.15 hits per line