supabase / supabase-flutter / 37622592489

92%

Build Type

push

github

Committed by web-flow

Commit Message

feat!: wrap transport failures and bring realtime into the SupabaseException hierarchy (#1928)

## What

Makes the exception hierarchy consistent across every client package, so
one `catch` covers a failure from any service and a transport failure
looks the same everywhere.

- **Transport failures are wrapped everywhere.** A request that never
received a response, because the connection failed, the request timed
out or the body stopped arriving, now throws a package exception that
mixes in the new `SupabaseTransportException`, with the originating
error in `cause`. `postgrest` and `supabase_storage` used to let the
HTTP client's `ClientException` or a `TimeoutException` through; they
now throw `PostgrestTransportException` and `StorageTransportException`.
`AuthRetryableFetchException`, `FunctionsFetchException` and
`IcebergNetworkException` already wrapped the failure and now mix in the
same marker and expose `cause`. A request aborted through its abort
signal still throws `RequestAbortedException`, and a `SupabaseException`
the HTTP client itself threw, such as the `AuthException` from
`AuthHttpClient` when a token refresh fails, passes through untouched
instead of being reported as an offline client.
- **Realtime joins the hierarchy.** `RealtimeException` extends
`SupabaseException`, with `RealtimeApiException` for a non-202 reply
from `httpSend()` (status, headers, body, request id) and
`RealtimeTransportException` for a timed-out or failed request. A join
the server declines, a binding mismatch and a failed `postgres_changes`
setup are reported on `onStatusChange` as `RealtimeException` with the
server's reason as the message. `RealtimeSubscribeException` in
`supabase` extends `RealtimeException`.
- **Misuse throws errors, not strings.** Calling `subscribe()` twice,
registering `postgres_changes` after `subscribe()`, pushing before
joining and returning `null` from an `onMessage` callback throw a
`StateError`; `ChannelEvent.fromValue` with an unkn... (continued)

Coverage Stats

169 of 173 new or added lines in 16 files covered. (97.69%)

34 existing lines in 5 files now uncovered.

9419 of 10280 relevant lines covered (91.62%)

5.26 hits per line