Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33
@@ -223,9 +223,12 @@ by a `data-import/` script, as README goal 12 asks.
|
||||
values, as the README's Library section promises: `datatype: boolean` over
|
||||
`{int(1,2)}` on an `int` field answers `prints an integer, not a boolean`.
|
||||
- Name the spelling to use in `checkNameHeld`'s and `checkNoOverlap`'s refusals, as the
|
||||
README's hold section promises: both answer "name the fields you want instead", and
|
||||
`{n} reaches "p" by a second route` names neither the read the route ends on,
|
||||
`{/row.p.last}`, nor the spelling to write, `{p.last}`.
|
||||
README's hold section promises: both answer "name the fields you want instead", or
|
||||
"reach it one way" for an operand, and `{n} reaches "p" by a second route` names
|
||||
neither the read the route ends on, `{/row.p.last}`, nor the spelling to write, `{p.last}`.
|
||||
- Split the README's linked-tables paragraph opening "A path descends from a row", 23
|
||||
lines holding five rules: move its load errors that are no overlap to the table
|
||||
section, and drop its bare `{/city}` refusal, which the hold section states.
|
||||
- Offer `move {Y} into a field with a drawGroup` in `overlapError` where both reads share
|
||||
one field: `"a":"{/cat} {/cat.p.first}"` ends at "name the fields you want instead",
|
||||
while the same pair in a format offers the move, which loads there too.
|
||||
|
||||
Reference in New Issue
Block a user