Skip to content

[email protected] unable to create sub-component correctly on Windows #1719

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
doggy8088 opened this issue Aug 17, 2016 · 6 comments · Fixed by #1961
Closed

[email protected] unable to create sub-component correctly on Windows #1719

doggy8088 opened this issue Aug 17, 2016 · 6 comments · Fixed by #1961
Assignees
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@doggy8088
Copy link
Contributor

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

    Windows 10

  2. 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.11-webpack.2
    node: 6.2.2
    os: win32 x64

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

    ng g c aa
    ng g c aa/bb

    The app.module.ts will produce a error syntax on BbComponent module path.

    image

  4. The log given by the failure. Normally this include a stack trace and some
    more information.

    unable to build.

  5. Mention any other details that might be useful.

    image
    image

@doggy8088 doggy8088 changed the title [email protected] unable to create sub-component on Windows [email protected] unable to create sub-component correctly on Windows Aug 17, 2016
@filipesilva filipesilva added type: bug/fix command: generate P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Aug 23, 2016
@filipesilva
Copy link
Contributor

Thank you for the very detailed report! We'll get on this bug asap.

@shairez
Copy link
Contributor

shairez commented Sep 9, 2016

@hansl please assign this to me, I'll have a go

@shairez
Copy link
Contributor

shairez commented Sep 9, 2016

@hansl well bummer, just finished writing a fix and then I saw this one -
#1961

I wrote the replace on the actual blueprint, but the above PR fixes the issue in a better place
:)

@hansl
Copy link
Contributor

hansl commented Sep 10, 2016

@shairez If the author of that PR does not answer to my comments before next week (say, Monday afternoon), you're welcome to make a PR of your own. That PR has a bug and I cannot let it in.

@shairez
Copy link
Contributor

shairez commented Sep 10, 2016

@hansl I'm sure he'll answer soon, if not, I'm on 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.

4 participants