-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
load collection path from nest-cli.json
#954
Comments
Setting |
yes, it does not work. always use |
Would you like to create a PR for this issue? |
sorry for the response you late. is that PR ok? |
I don't think this PR is really what you need because t makes it so the |
@rthomps7 would you like to create a PR with a fix? |
Hi, @kamilmysliwiec could you review PR #1166 that addressing that issue? Generally, I've used @rthomps7 suggestion and it worked. |
Let's track this here #1166 |
I'm submitting a...
Current behavior
collection default value is
@nestjs/schematics
. if we want to use custom schematics. I must executenest g -c custom/schematics
Expected behavior
nest-cli.json
. if I set the"collection": "@custom/schematics"
when I execute
nest g
it can load my custom schematics@nestjs/schematics
.What is the motivation / use case for changing the behavior?
Generate files by custom schematics more convenient
The text was updated successfully, but these errors were encountered: