supabase / supabase-flutter / 32465485913

89%

Build Type

push

github

Committed by web-flow

Commit Message

refactor(postgrest)!: make the rest client and builders stateless (#1748)

## Summary

Ports the stateless PostgREST refactor from supabase/supabase-swift#1240
to the Flutter SDK, in the idiomatic Dart shape. The builder chain here
was already made up of immutable value types sharing one request config,
and the per-request `accessToken` callback already landed in #1742, so
this PR covers the remaining pieces:

- `PostgrestQueryBuilder` and `PostgrestRpcBuilder` no longer extend the
executable builder, so a request without a table operation no longer
compiles. `await supabase.from('countries')`, which used to compile and
throw an `ArgumentError` at runtime, is now a compile-time error, and
`withConverter()`/`abortSignal()` are only reachable after
`select`/`insert`/`upsert`/`update`/`delete`/`count`. `setHeader()` and
`retry()` stay available on the query phase, since they meaningfully
configure whichever request follows. This is the Dart equivalent of the
Swift phantom-typed phase graph, expressed through the class hierarchy
instead.
- `PostgrestClient.headers` is now an unmodifiable map, making the
client fully stateless after construction.
- `SupabaseClient.rest` is no longer a mutable singleton: assigning
`SupabaseClient.headers` replaces the rest client instead of mutating
its header map in place, and `SupabaseClient.rpc()` no longer
permanently merges the client headers into the rest client on every
call.
- `SupabaseQuerySchema` drops its separate `headers` parameter; the
headers of the rest client it wraps are the single source.
- `PostgrestQueryBuilder` drops its type argument, which only mattered
while the builder was awaitable: `insert`/`upsert`/`update`/`delete`
without a trailing `select()` now resolve to `void` everywhere, instead
of `void` from a standalone `PostgrestClient` but `dynamic` from
`supabase.from()`.
-
`PostgrestBuilder.appendSearchParameters()`/`overrideSearchParameters()`
are removed from the public API; they were internal U... (continued)

Coverage Stats

133 of 145 new or added lines in 8 files covered. (91.72%)

7 existing lines in 2 files now uncovered.

5900 of 6663 relevant lines covered (88.55%)

4.36 hits per line