Keys
| Field | Type | Required | Description |
|---|---|---|---|
definitions | string[] | What genctl apply, types and schema read when given no -f: files or globs (** matches any depth), resolved against this file. | |
resolvers | Resolver[] | Source resolvers, tried in order and taken first-match on name and suffix; the built-in “process” is appended last, so listing one under that name overrides it. |
Resolver
One entry of resolvers.
| Field | Type | Required | Description |
|---|---|---|---|
command | string[] | yes | The resolver binary and its arguments, run from this file’s directory with the manifest on stdin. |
name | string | yes | What a directive names: ”$<name>: <argument>”. |
phase | code | structural | yes | What the resolver may do. “code” fills a slot with text and runs after inference, with types in hand; “structural” fills a slot or spreads a mapping with any value and runs before it, so it is handed no types. |
ext | string[] | Argument suffixes this resolver accepts (“.ts”, “.genroc.yaml”). Whole suffixes, not extensions; empty accepts anything. | |
types | object | Declarations the resolver wants generated, as name to address: a genctl schema type address, relative to the task the directive sits in, e.g. task.action.input.input. |