feature request: generators can generate where we want them to

[wbhob]

Bug Report or Feature Request (mark with an x)

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

Versions.

@angular/cli: 1.0.0
node: 6.9.4
os: darwin x64
@angular/common: 4.0.2
@angular/compiler: 4.0.2
@angular/core: 4.0.2
@angular/forms: 4.0.2
@angular/http: 4.0.2
@angular/material: 2.0.0-beta.3
@angular/platform-browser: 4.0.2
@angular/platform-browser-dynamic: 4.0.2
@angular/platform-server: 4.0.2
@angular/router: 4.0.2
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.2

Repro steps.

The log given by the failure.

Desired functionality.

Ionic has great generators that generate into a directory that is relevant to what you are generating. For example, 'pages' go into the pages directory, pipes go into their own directory, and providers go into their own directory. The Angular CLI currently puts everything into the app directory, which can be extremely disorganized for larger projects. Please consider a generation tree like this one:

src
    - app
        - app.module.ts
        - app.component.ts
        - app.component.html
        - app.component.(s)css
    - components
        - comp-name
            - comp-name.component.ts
            - comp-name.component.html
            - comp-name.component.(s)css
    - pipes
        - pipes.module.ts
        - pipe-name
            - pipe-name.pipe.ts
            - pipe-name.pipe.spec.ts
    - providers
        - providers.module.ts
        - provider-name
            - provider-name.provider.ts
            - provider-name.provider.spec.ts

Mention any other details that might be useful.

https://www.github.com/driftyco/ionic-cli

[clydin]

The CLI follows the style guide which emphasizes a directory hierarchy based on features. This lends itself directly to the Angular module concept wherein an application is a hierarchy of reusable (and potentially lazy loaded) modules.

[delasteve]

Also, this is essentially a dupe of #5995

[sumitarora]

Closing as above being track on #5995

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