The codegen allows specifying scripts it can run for you in certain events.
You can specify hooks on the root level or specify hooks on the output level (only some of them).
Each hook has its arguments, and it passes them to your scripts using
Add your scripts to your
codegen.yml file, and specify the scripts you wish to run, for example:
hooks: afterOneFileWrite: - prettier --write
Or, for specific output:
generates: ./src/types.ts: hooks: afterOneFileWrite: - prettier --write plugins: - typescript
The following lifecycle hooks are supported on the root level:
Triggered with no arguments when the codegen starts (after the
codegen.yml has been parsed).
Triggered every time a file changes when using watch mode.
Triggered with two arguments: the type of the event (for example,
changed) and the file's path.
Triggered in case of a general error in the codegen. The argument is a string containing the error.
Executed after the codegen has created the output and before writing the files to the file system.
Triggered with multiple arguments - paths for all relevant files.
Not all the files will be written to the file system, because this is triggered before checking if the file has changed since last execution.
Triggered before a file is written to the file system. Executed with the path for the file.
If the content of the file hasn't changed since the last execution - this hook won't be triggered.
Triggered after a file is written to the file system. Executed with the path for the file. If the content of the file hasn't changed since the last execution - this hook won't be triggered.
Executed after writing all the files to the file system. Triggered with multiple arguments - paths for all files.
Triggered with no arguments, right before the codegen closes or when watch mode is stopped.
The following hooks are available for a single output file:
Output level hooks are triggered before root level hooks.