fix(@angular/cli): ng completion
inside of ng app folders warns but does not produce output
#7366
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, while the global ng CLI is more recent, one cannot perform ng completion INSIDE that app folder.
This is due to the warning being written to stdout, which if appended to ~/.bashrc causes the shell to fail to process the English text as commands.
The solution is to display the warning to stderr without producing the completion output.
Also, an error code 1 is returned.
This PR fixes #6343.
The change introduces a breaking change, the warning is written to stderr - if the call is
ng completion
in an ng app folder.