@nx/nest:controller
Nest Controller Options Schema.
Usage
1nx generate controller ...
2By default, Nx will search for controller in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
1nx g @nx/nest:controller ...
2Show what will be generated without writing to disk:
1nx g controller ... --dry-run
2Options
name
Required
string
The name of the controller.
directory
string
Directory where the generated files are placed. when --nameAndDirectoryFormat=as-provided, it will be relative to the current working directory. otherwise, it will be relative to the workspace root.
language
string
Accepted values:
js, tsNest controller language.
module
string
Allows specification of the declaring module.
nameAndDirectoryFormat
string
Accepted values:
as-provided, derivedWhether to generate the component in the directory as provided, relative to the current working directory and ignoring the project (as-provided) or generate it using the project and directory relative to the workspace root (derived).
skipImport
boolean
Default:
falseFlag to skip the module import.
unitTestRunner
string
Default:
jestAccepted values:
jest, noneTest runner to use for unit tests.
skipFormat
Internal
boolean
Default:
falseSkip formatting files.
flat
Deprecated
boolean
Default:
falseFlag to indicate if a directory is created.
Provide the directory option instead and use the as-provided format. It will be removed in Nx v20.
project
pDeprecated
string
The Nest project to target.
Provide The directory option instead and use the as-provided format. the project will be determined from the directory provided. It will be removed in Nx v20.