Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33
@@ -114,4 +114,4 @@ In [docs/decisions.md](docs/decisions.md):
|
|||||||
- comprehension floor: every dimension and the overall at 7.0 or above; item 5 scores the restructure, which ships unscored: every `{…}` drawing afresh, the moves into `internal/`, and items 101, 102 and 104 to 106
|
- comprehension floor: every dimension and the overall at 7.0 or above; item 5 scores the restructure, which ships unscored: every `{…}` drawing afresh, the moves into `internal/`, and items 101, 102 and 104 to 106
|
||||||
- The template engine stays the root package until item 107; what reads no engine type sits in `internal/`, and items 101 and 102 move a table's rows there
|
- The template engine stays the root package until item 107; what reads no engine type sits in `internal/`, and items 101 and 102 move a table's rows there
|
||||||
- Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape
|
- Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape
|
||||||
- Goal 7.2 aims for a first template that can be written with no escape, not for templates that never need one
|
- Goal 7.2 holds while a first template can be written with no escape; a literal brace still takes `{{` or `}}`
|
||||||
|
|||||||
+5
-5
@@ -850,9 +850,9 @@ the README's Format string section states. The maintainer ruled the escape impli
|
|||||||
goal: doubled braces and a lone `}` belong to the `{…}` syntax, so the goal names no escape and
|
goal: doubled braces and a lone `}` belong to the `{…}` syntax, so the goal names no escape and
|
||||||
a lone `}` stays an error. Valid while a template escapes a brace by doubling it.
|
a lone `}` stays an error. Valid while a template escapes a brace by doubling it.
|
||||||
|
|
||||||
## Goal 7.2 aims for a first template that can be written with no escape, not for templates that never need one
|
## Goal 7.2 holds while a first template can be written with no escape; a literal brace still takes `{{` or `}}`
|
||||||
|
|
||||||
2026-10-05, Lilleman auf Larv. Serves goal 7.2. A goal is an aim, not a promise: it is enough
|
2026-10-05, Lilleman auf Larv. Serves goal 7.2. Goals are aims: it is enough that a first
|
||||||
that a first template can be written with no escape and no options, as `{first} {last}` is. A
|
template can be written with no escape and no options, as `fejkdata 'name: {/sv_SE.person.last}'`
|
||||||
template that wants a literal brace writes `{{` or `}}`, and that does not work against the
|
is. A template that prints a literal brace writes `{{` or `}}`, and the goal allows that. Valid
|
||||||
goal. Valid while a template needs an escape only to print a brace.
|
while `{{` and `}}` are the template syntax's only escape.
|
||||||
|
|||||||
Reference in New Issue
Block a user