Skip to content

Module generation fails to create component for multi-word module names #2724

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
Meligy opened this issue Oct 16, 2016 · 2 comments
Closed
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@Meligy
Copy link
Contributor

Meligy commented Oct 16, 2016

Please provide us with the following information:

OS?

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

macOS Sierra

Versions.

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

angular-cli: 1.0.0-beta.17
node: 6.7.0
os: darwin x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

ng new GreatApp
cd GreatApp
ng g module TwoWords

The log given by the failure.

Normally this include a stack trace and some more information.

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing module
  create src/app/two-words/two-words.module.ts
installing component
Invalid path: "/Users/Meligy/Code/temp/GreatApp/src/app/TwoWords"" is not a valid path.

Mention any other details that might be useful.

[UPDATED]

  • Notice how generating the app worked even though GreatApp consists of 2 words
  • Single-word names work just fine (ex: ng g module Word)
  • Generating TwoWords components directly works just fine too (ex: ng g component TwoWords)
  • Adding --routing to ng new and/or ng g module makes no difference
  • I have also tested with latest linked CLI with no luck

Thanks! We'll be in touch soon.

@filipesilva
Copy link
Contributor

@Brocco can you have a look?

@filipesilva filipesilva added the needs: investigation Requires some digging to determine if action is needed label Oct 17, 2016
Brocco added a commit to Brocco/angular-cli that referenced this issue Oct 18, 2016
@Brocco Brocco removed the needs: investigation Requires some digging to determine if action is needed label Oct 18, 2016
@Brocco Brocco added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix command: generate labels Oct 18, 2016
kieronqtran pushed a commit to kieronqtran/angular-cli that referenced this issue Oct 21, 2016
@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