ng generate <blueprint> assumes top level component is named "app"

[SanderElias]

Bug Report or Feature Request (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

1.0

Repro steps.

Generate an app. Manually rename 'top component'
I have done this in this repo

now generate a new component/class/whatever.

The log given by the failure.

The above steps will create an app folder, and put the generated files in there.

Desired functionality.

Files should get generated in the right place, in my sample that's the shell folder.

Mention any other details that might be useful.

I believe this line is responsible

[SanderElias]

@sumitarora Any progress? Is there something I can do?

[hansl]

This is a hard problem (since it's fixed in a lot of places), but fixable. @sumitarora do you need any help?

[pkamdem]

@sumitarora @hansl any update on this one?

Thanks for the great work guys!

[somombo]

looks like #6079 fixes this

[Brocco]

This issue was resolved with the introduction of schematics as the "blueprint" engine for the CLI.

[angular-automatic-lock-bot]

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.}