declarative-definitions · V1
A control is more than a name.
It is a definition.
A table. A select. A form. We know what these controls are. But when we build one, we still need to answer a more useful question: which kind of table, and what should that particular table contain?
This is the story of how definitions give that answer in a simple, consistent shape.
The idea in one glance
Three layers. One easy way to read them.
01 · CONTROLtableWhat kind of control?
→
02 · VARIATIONbodyOnlyWhich form of that control?
→
03 · CONTRACTbaseFromSpec
instructions
optionsWhat describes this variation?
instructions
optionsWhat describes this variation?
The first layer names the control. The second names a particular variation. Every variation then follows the same third-layer contract.
Follow the chapters
One idea at a time.
Keep this thought: A definition does not try to be the table itself. It describes which starting spec, which instructions, and which options belong to a particular table variation.