Documentation
¶
Overview ¶
Package codegen orchestrates the offline device-management code generator: it loads the committed spec snapshots, clears previously generated output (identified by the DO-NOT-EDIT header), builds view models (build), renders them through the template firewall (render) and assembles files (fileasm). Everything is deterministic from metadata/specs.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
This section is empty.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package build flattens parsed specs into fully-resolved view models.
|
Package build flattens parsed specs into fully-resolved view models. |
|
Package fileasm is the single choke-point for generated-file scaffolding: the DO-NOT-EDIT header, package clause, grouped imports and gofmt.
|
Package fileasm is the single choke-point for generated-file scaffolding: the DO-NOT-EDIT header, package clause, grouped imports and gofmt. |
|
Package naming holds the spec-to-Go identifier rules shared by every emitter.
|
Package naming holds the spec-to-Go identifier rules shared by every emitter. |
|
Package render is the firewall between view models and Go source: view models go in, source fragments come out, and the only mechanism is text/template execution over the embedded .tmpl files.
|
Package render is the firewall between view models and Go source: view models go in, source fragments come out, and the only mechanism is text/template execution over the embedded .tmpl files. |
|
Package view defines the pure-data models the templates render.
|
Package view defines the pure-data models the templates render. |
Click to show internal directories.
Click to hide internal directories.