Name goal 4's check and the rewrite the refusal offers, scope the render-draw decision to unselected paths, and state the step-up clash
This commit is contained in:
@@ -48,8 +48,9 @@ This round, in order:
|
||||
path `Fake` accepts, which a selector is too. Delete the dead `table.descends` and
|
||||
the redundant `string(key)` in `checkNoRepeatedItem`.
|
||||
- Delete the decision "The rows of a table are alternatives": it defines `alternatives`,
|
||||
which its comment in `family.go` already does, and the README's "which pairs are
|
||||
weighed against each other" sends a reader to the log for that definition.
|
||||
which its comment in `family.go` already does. Point the README's "which pairs are
|
||||
weighed against each other" at that comment's rule, stated in the README's Table
|
||||
section, where it sends a reader to the log for the definition today.
|
||||
- Run the nine-seat panel again and file what it names here.
|
||||
|
||||
### Data
|
||||
@@ -174,10 +175,11 @@ by a `data-import/` script, as README goal 12 asks.
|
||||
- Render selected rows as the decision "A selected row is fixed, not drawn, and an
|
||||
unnamed read beside it is refused" states: `New` refuses
|
||||
`{/misc.territory[SE].capital} / {/misc.territory[FI].capital}` today, and a choice
|
||||
whose items select different rows. Have the refusal of an unnamed read name a
|
||||
selected path that loads: beside `{/geo.SE.locality[Lund].name}`,
|
||||
`{/geo.SE.municipality.name}` names none today, and the one that holds selects from
|
||||
the top, `{/geo.SE.municipality[Lund].name}`.
|
||||
whose items select different rows. Have the refusal of an unnamed read name the
|
||||
rewrite through each selection, selecting an ancestor of the selected row by key:
|
||||
beside `{/geo.SE.locality[Lund].name}`, `{/geo.SE.municipality.name}` names none
|
||||
today, where `{/geo.SE.municipality[1281].name}` holds. Scope the README's "A reference
|
||||
path into a category is held" to a path that selects no row.
|
||||
- Report the same error every load for a table with two bad options, and for a
|
||||
folder with two unnamed rows files: `readTableOptions` and `loadDir` return on the
|
||||
first in Go's map order.
|
||||
@@ -218,10 +220,13 @@ by a `data-import/` script, as README goal 12 asks.
|
||||
|
||||
### Open questions to settle
|
||||
|
||||
- Decide whether a path steps from a row up to its parent, so
|
||||
`{/geo.SE.locality[Lund].municipality.name}` reads Lund's municipality: three simulated
|
||||
template writers all expected it to, per goal 4, and today it fails with "municipality
|
||||
is a column, and a cell holds no fields". Adding it only accepts a refused spelling.
|
||||
- Decide how a path steps from a row up to its parent row: three simulated template
|
||||
writers expected `{/geo.SE.locality[Lund].municipality.name}` to read Lund's
|
||||
municipality, which goal 4 asks for, but `.municipality` after a row is already the
|
||||
link column's cell, `city[Oslo].country` rendering `NO`. So either the name means the
|
||||
cell where it ends a path and the parent row where a segment follows, which the
|
||||
decisions "One name, one meaning" and "`parent` names the link column and the table
|
||||
alike" have to allow, or the step up takes a spelling of its own.
|
||||
- Decide whether a goal 5 violation joins the comprehension gate's exception list: the
|
||||
`{/sel}|{/sel}` panic waits behind the whole round at 5.9, and
|
||||
`{/geo.SE.locality}|{/geo.SE.municipality}` mispairs the shipped data meanwhile, though a
|
||||
|
||||
Reference in New Issue
Block a user