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

Answer the step-up question at goal level: a path renders what every writer expects, so a link column steps up to its parent and may not end a path

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-09-27 16:41:31 +02:00
committed by Lillem4n
parent 543b21d99f
commit f8e9d9a280
4 changed files with 31 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
todo.md
+9 -22
View File
@@ -172,14 +172,19 @@ by a `data-import/` script, as README goal 12 asks.
### Library and CLI
- Step up from a row to its parent as the decision "A link column after a row steps up
to the parent row, and a path may not end on it" states: `city[Oslo].country.name` is
a load error today, and `city[Oslo].country` renders the cell `NO`. Correct the
README's `city[Oslo].country` example to match.
- 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 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.
rewrite through each selection: beside `{/geo.SE.locality[Lund].name}`,
`{/geo.SE.municipality.name}` names none today, where
`{/geo.SE.locality[Lund].municipality.name}` holds once the step up above lands.
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.
@@ -220,24 +225,6 @@ by a `data-import/` script, as README goal 12 asks.
### Open questions to settle
- Decide how a path steps from a row up to its parent row, one level per step, chained.
Three simulated template writers expected `{/geo.SE.locality[Lund].municipality.name}`
to read Lund's municipality; today it is a load error, since `.municipality` after a
row is the link column's cell, `city[Oslo].country` rendering `NO`. The options:
- The name means the parent row where a segment follows, and the cell where the path
ends. It gives a refused spelling a meaning, so a minor, and extends "After a row, a
path names a column or a linked table" from child tables to the parent.
- The name always means the parent row, rendering through its format where the path
ends: `city[Oslo].country` renders `Norway`, the cell stays reachable through the
parent's key column. A change
to what exists, so a major, and a record's `country` column then holds the key while
the path renders the name.
- Goal 4 refuses a path ending on the name, since a writer could expect the code or the
name, naming the parent's key column and `.name`. A major.
Each option gives `locality[Lund].municipality.name` and
`municipality[1281].name` one result, so goal 4's one spelling per result refuses one
of them, and the rewrite the selected-row item above names follows that choice.
- 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