supabase / supabase-swift / 33056961156
88%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 109
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 87.101% (+0.2%) from 86.941%
33056961156

push

github

web-flow 
docs(postgrest): stop describing a generated Update row shape (#1284)

`@Table` stopped generating a nested `Update` type when `PostgrestUpdate`
replaced the row-shaped update, and SDK-1622 removed the dead
`named(Update)` entry from the macro's names list. Five comments still
described the removed type.

The public DocC on `@PrimaryKey` was the one that mattered: it told
readers `Update` carries the key as an optional column. The claim
underneath it still holds — an update can assign the key like any other
column, so a natural key can be renamed — so it now points at
`PostgrestUpdate`, which is where that behavior actually lives.

`TableMacro.swift:201` justified keying the `= nil` default off the
generated parameter type rather than the property's own, using `Update`
as the example. The rule still holds for `Insert`, where `@Default` makes
a non-optional property's parameter optional, so only the example
changed.

In `Diagnostics.swift` and `StoredProperty.swift` the mention was
redundant rather than wrong: `PostgrestUpdate` resolves every column
through `columnName(for:)`, which both sentences already name, so a
dropped property's effect on updates was already covered.

The comments at `TableMacro.swift:85` and `:106`, and the one at
`PostgrestRelation.swift:63`, are left alone — they explain why the
shape does not exist.

Fixes SDK-1628

9244 of 10613 relevant lines covered (87.1%)

1011900.89 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33056961156.1 109
87.1
 GitHub Action Run
Source Files on build 33056961156