supabase / supabase-swift / 32830303852

87%

Build Type

push

github

Committed by web-flow

Commit Message

feat(postgrest): add @SelectionOf for column subsets (#1260)

* feat(postgrest): add @SelectionOf for column subsets

The expansion emits references to the relation's own columns, so a
property that names no column on it is a compile error. Embeds via
@Relationship are deliberately out of scope for this slice.

Also closes the hole the RFC's headline decision 8 asks for and the
protocol did not enforce. `PostgrestSelection` gains `associatedtype
Source: PostgrestRelation`, fixed to `Self` by a same-type constraint on
the `PostgrestRelation` refinement, so a hand-written relation conformance
declares nothing new. `select(_:)` is then gated on `S.Source == R`, and
handing a selection to the wrong relation is no such overload rather than
a PostgREST 400.

@SelectionOf follows the same two rules @Table had to learn: everything is
emitted from the extension role, and the inheritance clause names the
whole refinement chain. The shared `codingKeys` and `inheritanceClause`
helpers move to Support/Generation.swift so a relation and a selection of
it cannot spell the same column differently.

* chore(compliance): register @SelectionOf and the selection source

`PostgrestTypedSource.select` is already attributed to
database.query.select, and the new overload shares that symbol name, so
only the macro attribute and the new associated type are added.

* fix(postgrest): read a selection's columns from the relation, not its own names

A selection knows its property names; it does not know what column the
relation maps them to. `selectString` snake-cased locally, which is wrong the
moment the relation carries a `@Column`:

    @Table("todos")
    struct Todo {
      @Column("due_at") var dueDate: Date?
    }

    @SelectionOf(Todo.self)
    struct TodoDueDate {
      var dueDate: Date?      // asked PostgREST for `due_date`
    }

Verified before the fix: `selectString` was `"due_date"` while
`SelectionTodo.columnName(for: \.dueDate)` was `"due_at"`. PostgREST would
... (continued)

Coverage Stats

0 of 3 new or added lines in 1 file covered. (0.0%)

17 existing lines in 1 file now uncovered.

9196 of 10566 relevant lines covered (87.03%)

45.39 hits per line