feat(application): add spec option #1586
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: nestjs/nest-cli#2327
What is the new behavior?
The command
nest g app some-app --no-spec
will not add test files.Does this PR introduce a breaking change?
Other information
I've used unit tests to make sure the logic is correct, but I'm trying to use an
npm link
to get the local@nestjs/cli
to call my modified@nestjs/schematics
without success (when debugging@nestjs/cli
, I find that he prints out logs forbin/nest.js
, and logs for the other files don't show up).Maybe I've succeeded, but I'm not sure. 🤣