-
Notifications
You must be signed in to change notification settings - Fork 12k
ng help generate: crashes on Angular 5.2.2 #9412
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
Comments
Noticed this issue too because Webstorm is using this command to know the available things that generate can do. This issue seems to only exists on |
Dennis from WebStorm team here. I can confirm that this fails with the same output for me. We'll be releasing WebStorm 2017.3.4 with a workaround (loading predefined list if the command fails), but would love to get a proper fix. |
@denofevil, also experiencing the issue with 1.6.6. Thanks for your efforts on the workaround. @h-bex thanks for reporting the issue. |
I also noticed this due to the interaction with WebStorm. Actual generate commands still seem to work, and top level help seems to work, as does help on other commands... just not for the generate command. |
Same here on 1.6.6 in Webstorm. Updated Angular CLI because of another bug, so I'll have to manually (cmd) generate my components for now. |
Is this fixed in 1.6.7? |
This is not fixed in 1.6.7:
The behavior of the help generate command:
|
Sorry; wrong button; have to reopen it again. |
Hi everyone! This is the version I've got installed in my lap:
/ △ \ | '_ \ / Angular CLI: 1.6.7 Thanks in advance... |
Same issue here with the "ng g --help" command.
Angular CLI: 1.6.7 @angular/cdk: 5.2.0 C:\Code\angularmaterial>ng g --help |
Still occurs on 1.7.0-rc.0
Really missing this functionality in IntelliJ ._. |
Still occurs with 1.6.8
|
Same issue with Webstorm 2017 3.4
|
Confirmation: Bug has been fixed with Angular 1.7.0:
Output:
Result: Works as expected. Thank you! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
Observed behavior
Desired behavior
Mention any other details that might be useful (optional)
N/A
The text was updated successfully, but these errors were encountered: