From 672263421ab9f1c51e429dc52c077251d6131b83 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Tue, 29 Sep 2026 16:38:20 +0200 Subject: [PATCH] File the operand route's missing spelling under the refusal-spelling item --- todo.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/todo.md b/todo.md index b8d927f..6f1dfbd 100644 --- a/todo.md +++ b/todo.md @@ -252,7 +252,10 @@ by a `data-import/` script, as README goal 12 asks. `{int(1,2)}` on an `int` field answers `prints an integer, not a boolean`. - Name the spelling to use in `checkNameHeld`'s path refusal and `checkNoOverlap`'s, 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}`. + 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}`. Where an operand route's value + is the held name, offer it as the operand: `lowercase operand "y" renders + "/misc.territory"` ends at "stop", where `{lowercase(/misc.territory)}` loads. - 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.