Rewrap the render-draw decision

This commit is contained in:
2026-09-27 15:03:27 +02:00
committed by Lillem4n
parent 98b25177e7
commit 430bdbcaae
+3 -4
View File
@@ -218,10 +218,9 @@ handle is needed, as the cache already compiles once.
## A render shares one reference draw per category, per group ## A render shares one reference draw per category, per group
Every reference path into a category that selects no row, in one `Fake` or one record, Every reference path into a category that selects no row, in one `Fake` or one record,
reads one draw of it, reads one draw of it, so a value's facts agree across its fields, nested templates and
so a value's facts agree across its fields, nested templates and columns alike — columns alike — `{/currency.code}` in one field and `{/currency.symbol}` in another name
`{/currency.code}` in one field and `{/currency.symbol}` in another name one currency, one currency, whichever view renders them. A `repeat` iteration is a render of its own, since
whichever view renders them. A `repeat` iteration is a render of its own, since
repeating asks for another entity, and a [draw group](../README.md#draw-group) names further repeating asks for another entity, and a [draw group](../README.md#draw-group) names further
entities within one render, so a payer and a payee are two groups over one `person` entities within one render, so a payer and a payee are two groups over one `person`
rather than two copies of it. Only references share: a sibling field is local to its own rather than two copies of it. Only references share: a sibling field is local to its own