Skip to content
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

fix(@angular/cli): ng completion inside of ng app folders warns but does not produce output #7246

Conversation

catull
Copy link
Contributor

@catull catull commented Aug 2, 2017

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 places
such 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 version
issues 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.

If an ng app folder was created with an older CLI version, then 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 places
such as shell start-up code, for which the completion is meant in the first place.
The completion call perfoemd in an ng app folder generated with an older version
issues a warning, which the shell cannot ignored, but tries to interpret as genuine
commands, and thus it fails miserably then and there.

The change constitute a breaking change, because previously `ng completion` could be
called from `everywhere`.
@catull catull changed the title fix(@angular/cli): allow ng completion only outside of ng app folders fix(@angular/cli): ng completion inside of ng app folders behave again Aug 3, 2017
@catull catull closed this Aug 11, 2017
@catull catull deleted the fix-6343-allow-ng-completion-only-outside-of-ng-app-folders branch August 11, 2017 22:56
@catull catull changed the title fix(@angular/cli): ng completion inside of ng app folders behave again fix(@angular/cli): ng completion inside of ng app folders warns but does not produce output Aug 11, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng completion -b >> ~/.bashrc fails if local cli version is different from global cli version
2 participants