Generators specify the mapping from inputs to templates.
They will have input schema(s) and some configuration options for users,
and map the
In field to the
Out field for
hof to process.
HofGenerators and Files have their own schemas. Only the core fields are shown here. You can find the real schemas in the hof repository.
Mapping In to Out
Your goal as a generator writer is to fill in the
Out field from the
In field will be passed through the templates and partials
if they are defined in the
In represents the data presented to the templates.
- You can have your users set values in meaningful fields and collect them
- You can add any other separate or calculated data
- The top-level
Inis passed to all templates and can be extended with the per-template field
Out holds the files to be rendered by hof
- Is a list of
HofGeneratorFiles, where each…
- Has a filepath for where it will be written under
- Has an
Invalue which will be unified with the top-level
There are typically two types of files (templates)
- Files which are generated once per application. Think of a
index.js. We often call these “once” files or templates.
- Files which are generated for each sub-resource. These might be routes in a server or commands in a CLI. We often call these “repeated” files or templates.
You can use as many helper fields or calculations as you want
- Calculate commonly used fields or values for
- Interpolate common base paths for filepaths
- Create file lists for repeated templates.