A project's own generators join the shared one
A project's own guidelines may add generators of code, listed in a rule of theirs refining this one with what each writes from which nodes. A project's generator writes the same from the same nodes, and what it writes waits for that rule as for the nodes it is written from (§s-kh8qcd5kxgh9z3j).
Code generated from a project's own kinds of node and fields is written by no generator of the SpecSheriff guidelines. A copy is checked against what its nodes produce only where the same nodes always produce the same; code from a generator whose rule is unconfirmed implements what nobody confirmed (§s-utvqbypzhmgndug).
The links it makes
The links made to it
- cites ← The nodes are the specification
- cites ← The system's code is the code implementing the specification, and its tests
- cites ← A project's own checks and generators are tested against the rule listing them
- cites ← The reviewer sees only the change and the nodes it names
- cites ← Where the files are
- implements ← The commands
- implements ← Generated copies against the nodes
The decisions taken on it
- Problem
Code a project generates from its own kinds and fields, as runtime checks, enumerations or a registry its runtime reads, had no generator of SpecSheriff to write it and nothing holding it to its nodes.
- Ruling
The owner: a project's own generators are listed in one rule of its own guidelines with what each writes from which nodes; what one writes is held as the generated types are, waiting for that rule as for its nodes, and the generator writes the same from the same nodes.