supabase / supabase-swift / 29498521121

84%

Build Type

push

github

Committed by web-flow

Commit Message

feat(postgrest): add notIn filter, dryRun and maybeSingle modifiers (#1114)

* feat(postgrest): add notIn filter, dryRun and maybeSingle modifiers

Closes remaining SDK-1298 query builder gaps: `notIn(_:values:)` filter,
`dryRun()` (Prefer: tx=rollback), and `maybeSingle()` which returns nil
instead of throwing when a query matches zero rows.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* test(postgrest): add integration tests for notIn, dryRun, maybeSingle

Verified end-to-end against a local Supabase instance. dryRun can only
smoke-test the request succeeds — actual rollback requires PostgREST's
db-tx-end setting, which the Supabase CLI dev config doesn't expose;
the Prefer header itself is covered by the PostgREST unit tests.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* test(postgrest): verify dryRun actually rolls back via db_tx_end role setting

PostgREST's db-tx-end can be set per-role via `ALTER ROLE authenticator
SET pgrst.db_tx_end`, same as postgrest-js's own test setup — my earlier
assumption that it required a process-level env var (unreachable via the
Supabase CLI) was wrong. With this enabled, testDryRunOnUpdate now
asserts the update was genuinely rolled back, not just that it didn't
error.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* chore: register notIn/dryRun/maybeSingle in sdk-compliance.yaml

CI's public API check flagged these 3 new symbols as unregistered.

---------

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

Coverage Stats

34 of 34 new or added lines in 3 files covered. (100.0%)

140 existing lines in 5 files now uncovered.

8061 of 9628 relevant lines covered (83.72%)

38.53 hits per line