supabase / supabase-flutter / 38391038446

92%

push

github

fix!: decode unknown server values for open-set enums instead of throwing (#1953)

Decoding a server response no longer throws when an enum field holds a
value this version of the SDK does not know. A new server value
previously broke the whole response with a `StateError` or
`ArgumentError`.

These enums gain an `unknown` value, the same pattern `FactorType`,
`FactorStatus` and `GenerateLinkType` already use:

- `supabase_auth`: `OAuthClientType`, `OAuthClientRegistrationType`,
`OAuthClientGrantType`, `OAuthClientResponseType`, `CustomProviderType`
- `supabase_storage`: `LifecycleRuleStatus`
- `supabase_realtime`: `PostgresChangeEvent`, `PresenceEvent`
- `iceberg`: `NullOrder`, `SnapshotReferenceType`

`SortDirection` is the exception. It is shared with PostgREST and
storage ordering, where an `unknown` value would be something a caller
could send. Instead, `SortDirection.fromValue` returns `null` for an
unknown value, the same as the vector enums, and `SortField.direction`
is nullable.

Most of these enums are also request inputs, so `unknown` is refused on
the way out. Building a request with it throws an `ArgumentError`
instead of sending `unknown` to the server. This covers OAuth client
grant and response types, custom provider creation and the
`listProviders` filter, lifecycle rules, `onPostgresChanges`, and
iceberg sort fields and snapshot references (including a `SortField`
without a direction).

Linear: SDK-2127

55 of 66 new or added lines in 8 files covered. (83.33%)

9562 of 10427 relevant lines covered (91.7%)

5.27 hits per line