Skip to content

ng g --help advises us incorrectly #4802

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

Closed
johnpapa opened this issue Feb 17, 2017 · 3 comments · Fixed by #4880
Closed

ng g --help advises us incorrectly #4802

johnpapa opened this issue Feb 17, 2017 · 3 comments · Fixed by #4880
Assignees
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@johnpapa
Copy link
Contributor

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

Repro steps.

when running a command incorrectly we sometimes get a help message advising us how to get help. This is good. However it is not always working.

For example, I make this mistake (--dryrun should be --dry-run)

$ ng g c dashboard/foobar --dryrun
The option '--dryrun' is not registered with the generate command. Run `ng generate --help` for a list of supported options.

ok, so i run ng g —help and my output says ...

The ng generate --help command requires a name to be specified.

so i run $ ng g c —help and there is no output, but it seems there should be

cc @filipesilva

@filipesilva filipesilva added type: bug/fix P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Feb 19, 2017
@filipesilva
Copy link
Contributor

@sumitarora could this be related with your recent fix to ng help?

@sumitarora sumitarora self-assigned this Feb 21, 2017
@sumitarora
Copy link
Contributor

@filipesilva looking into it

@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants