larvit/fejkdata
3
0
Fork 0
Code Pull Requests 1 Actions Activity

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
pull from: worktree-todo-relative-dates-exact-counts
merge into: larvit:main
Conversation 0 Commits 966 Files Changed 167
+6 -3
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit c2ac7bf843 - Show all commits
todo.md
+6 -3
View File
@@ -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 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`. `{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 - 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 README's hold section promises: both answer "name the fields you want instead", or
`{n} reaches "p" by a second route` names neither the read the route ends on, "reach it one way" for an operand, and `{n} reaches "p" by a second route` names
`{/row.p.last}`, nor the spelling to write, `{p.last}`. 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 - 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", 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. while the same pair in a format offers the move, which loads there too.