28c53f942b
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> Artifact generators don't handle consistently receiving a file extension in the `path` option. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Artifact generators should handle receiving a file extension in the `path` option. If the file extension is passed, the file path will be treated as "complete" and used fully as provided. If the `path` provided doesn't contain a file extension, the default extension will be appended to it (or the one provided in a related option, e.g. `--language`, `--js`, etc) together with the suffix for generators that use it. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
46 lines
1.5 KiB
JSON
46 lines
1.5 KiB
JSON
{
|
|
"name": "interface",
|
|
"factory": "./src/generators/interface/interface",
|
|
"schema": {
|
|
"$schema": "https://json-schema.org/schema",
|
|
"$id": "NxNestInterfaceGenerator",
|
|
"title": "Nest Interface Options Schema",
|
|
"description": "Nest Interface Options Schema.",
|
|
"cli": "nx",
|
|
"type": "object",
|
|
"examples": [
|
|
{
|
|
"description": "Generate the interface `Foo` at `myapp/src/app/foo.interface.ts`",
|
|
"command": "nx g @nx/nest:interface myapp/src/app/foo.interface.ts"
|
|
},
|
|
{
|
|
"description": "Generate the interface without providing the file extension. It results in the interface `Foo` at `myapp/src/app/foo.interface.ts`",
|
|
"command": "nx g @nx/nest:interface myapp/src/app/foo"
|
|
}
|
|
],
|
|
"properties": {
|
|
"path": {
|
|
"description": "The file path to the interface. Relative to the current working directory.",
|
|
"type": "string",
|
|
"$default": { "$source": "argv", "index": 0 },
|
|
"x-prompt": "What is the interface file path?"
|
|
},
|
|
"skipFormat": {
|
|
"description": "Skip formatting files.",
|
|
"type": "boolean",
|
|
"default": false,
|
|
"x-priority": "internal"
|
|
}
|
|
},
|
|
"additionalProperties": false,
|
|
"required": ["path"],
|
|
"presets": []
|
|
},
|
|
"description": "Run the `interface` NestJS generator with Nx project support.",
|
|
"implementation": "/packages/nest/src/generators/interface/interface.ts",
|
|
"aliases": [],
|
|
"hidden": false,
|
|
"path": "/packages/nest/src/generators/interface/schema.json",
|
|
"type": "generator"
|
|
}
|