supabase / supabase-swift / 37350051879

95%

Build Type

push

github

Committed by web-flow

Commit Message

fix(postgrest)!: order() no longer forces NULLS LAST by default (#1417)

* fix(postgrest)!: order() no longer forces NULLS LAST by default

`order(_:ascending:nullsFirst:referencedTable:)` always appended a null
placement because `nullsFirst` defaulted to `false`, so every ordered
query sent `.nullslast` — including descending ones, where Postgres's
own default is `NULLS FIRST`. supabase-js only sends a placement when
the caller asks for one; an omitted `nullsFirst` should leave the
database default alone.

`nullsFirst` is now `Bool?`, defaulting to `nil`, and the query omits
the placement entirely when it is `nil`.

Fixes SDK-1633

* test(postgrest): drop the null placement from the timestamptz request snapshot

* fix(postgrest): update stale snapshot after order() default placement change

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Coverage Stats

2 of 2 new or added lines in 1 file covered. (100.0%)

7 existing lines in 2 files now uncovered.

10727 of 11914 relevant lines covered (90.04%)

109.35 hits per line