fix(@angular/cli): ng completion
inside of ng app folders warns but does not produce output
#7246
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.
If an ng app folder was created with an older ng CLI version, and the ng CLI is upgraded globally, one cannot perform
ng completion
INSIDE that app folder.Thus it is advisable to only allow
ng completion
in placessuch as shell start-up code, for which the completion is meant in the first place.
ng completion
performed in an ng app folder generated with an older versionissues a warning, which the shell cannot ignore, but tries to interpret as genuine
shell commands, miserably failing. This warning must be prepended with shell comment characters.
The PR fixes #6343.
The change does not introduce a breaking change, it prevents the warning from being erroneously
interpreted by the shell.