Answer stability round 1: the tests precede the code they pin, ErrNoColumns's doc speaks of itself alone, the edited docs are reflowed, and the binding hint and a JSON-shaped template's parse position are filed as items 228 and 229

This commit is contained in:
2026-10-11 23:27:59 +02:00
committed by Lillem4n
parent 18ba32e8cf
commit 90d1948a2b
4 changed files with 17 additions and 9 deletions
+3 -3
View File
@@ -392,9 +392,9 @@ A path, wherever a call takes one, may start with one `/`, as a reference does.
A `*Record` carries its columns via `Columns()` — each a `Column` of `Name`,
`DataType`, rendered `Value` and `Null` — and serializes them with `JSON()`
(one object), `CSVHeader()`/`CSVLine()`, or `SQLInsert(table)` — the shapes the
CLI's `--format` writes, each without a trailing newline. `FakeRecord` and `FakeRecordTemplate` take a record; a
path or template that is not one — a bare string, a choice of more than one item, or a
folder — errors.
CLI's `--format` writes, each without a trailing newline. `FakeRecord` and
`FakeRecordTemplate` take a record; a path or template that is not one — a bare string, a
choice of more than one item, or a folder — errors.
```go
type User struct {