Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33

Open
lilleman wants to merge 966 commits from worktree-todo-relative-dates-exact-counts into main
Showing only changes of commit f03a0de42c - Show all commits
+9 -10
View File
@@ -552,11 +552,10 @@ A path descends from a row to a linked table by name, at any depth, and `--list`
advertises each direct step. Within one render and [draw group](#draw-group), linked advertises each direct step. Within one render and [draw group](#draw-group), linked
tables agree: the first table a reference path reads pins its ancestors, and a tables agree: the first table a reference path reads pins its ancestors, and a
descendant read after it is drawn inside them, so `{/city.name}` and descendant read after it is drawn inside them, so `{/city.name}` and
`{/country.name}` are a city and its country whichever is read first, except a step down `{/country.name}` are a city and its country whichever is read first, except a step
after a `..` ([Step up](#step-up)). A selected row down after a `..` ([Step up](#step-up)). A selected row pins the render the same way,
pins the render the same way, so every reference path into one family of linked so every reference path into one family of linked tables in one render and group
tables in one render and group selects the same rows: one that selects none beside selects the same rows: one that selects none beside one that does is refused naming the spelling that does, `{/country[SE].city.name}`
one that does is refused naming the spelling that does, `{/country[SE].city.name}`
beside `{/country[SE].name}`, and two selecting different rows are refused naming a beside `{/country[SE].name}`, and two selecting different rows are refused naming a
`drawGroup` to draw them apart in. A bare `{/city}` beside a path into its family is `drawGroup` to draw them apart in. A bare `{/city}` beside a path into its family is
refused too, since a bare reference draws each time, and so is a path that draws a refused too, since a bare reference draws each time, and so is a path that draws a
@@ -585,13 +584,13 @@ fejkdata -d ./mydata 'city[Göteborg]..country.city' # Stockholm or Göteborg,
fejkdata -d ./mydata '{/city as c}{c}, {c..country.name}' # Oslo, Norway fejkdata -d ./mydata '{/city as c}{c}, {c..country.name}' # Oslo, Norway
``` ```
It steps up from a selected row, a drawn row or a [name](#names) bound to a row, one level It steps up from a selected row, a drawn row or a [name](#names) bound to a row, one
per `..`: `geo.SE.locality..municipality..region.name`. `.country` after a row still reads the link level per `..`: `geo.SE.locality..municipality..region.name`. `.country` after a row
column's cell, `NO`. still reads the link column's cell, `NO`.
After a `..`, `.` steps down again and draws afresh inside the row stepped up to, so After a `..`, `.` steps down again and draws afresh inside the row stepped up to, so
`city[Göteborg]..country.city` may draw Göteborg again. Paths stepping down from one `..` read one draw, as one `city[Göteborg]..country.city` may draw Göteborg again. Paths stepping down from one
reference path does: `{/city..country.city.name}` and `{/city..country.city.population}` `..` read one draw, as one reference path does: `{/city..country.city.name}` and `{/city..country.city.population}`
describe one city, within a render and [draw group](#draw-group), or within a name's pick. describe one city, within a render and [draw group](#draw-group), or within a name's pick.
A `..` that names anything but the parent table is an error naming the parent. A selector A `..` that names anything but the parent table is an error naming the parent. A selector