supabase / supabase-flutter / 28951625246

86%

push

github

feat(functions): expose FunctionsFetchException/FunctionsRelayException/FunctionsHttpException subtypes (#1545)

## What

Introduces three error subtypes as subclasses of the existing
`FunctionException`, so consumers can match on the failure mode:

- **`FunctionsFetchException`** — network/transport failure reaching the
function, before any response is received. The originating error is
available in `details`; `status` is `0`.
- **`FunctionsRelayException`** — error returned by the relay, detected
via the `x-relay-error: true` response header.
- **`FunctionsHttpException`** — non-2xx response from the function
itself.

`invoke()` now throws the appropriate subtype depending on the failure
mode.

## Naming

The subtypes use the `Exception` suffix (not `Error`) to follow Dart's
`Error`/`Exception` distinction: they are meant to be caught, extend
`FunctionException` (which implements `Exception`), and wrap an
underlying `ClientException`. This also keeps them consistent with the
base class name.

## Why non-breaking

Existing `catch` blocks that catch `FunctionException` continue to work
unchanged; the new subtypes only refine the type consumers can
optionally match on. No existing signature or default behavior changes.
`toString()` now uses `\$runtimeType` so subtypes print their own name.

A follow-up for making `FunctionException` a `sealed` class (breaking,
enabling exhaustive `switch`) is tracked in #1550 for v3.

## Tests

Added `network-error` and `relay-error` fixtures to the custom HTTP
client, plus cases asserting each subtype is thrown, that
`status`/`details`/`reasonPhrase` are populated, and that the subtypes
remain catchable as `FunctionException`.

Closes SDK-1258

14 of 14 new or added lines in 2 files covered. (100.0%)

4464 of 5165 relevant lines covered (86.43%)

3.98 hits per line