Skip to content

Feature: When generating a NgModule, allow -m to indicate which NgModule should import it #5377

Closed
@johnpapa

Description

@johnpapa

OS

Mac OSX Sierra 10.12.3

Versions

@angular/cli: 1.0.0-rc.1
node: 6.9.1
os: darwin x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.1
@angular/compiler-cli: 2.4.9

Repro steps.

ng g m login -m app.module doesn't look for the -m option today . But i think it would be helpful to be able to create a NgModule and tell the CLI where you want it imported (in another module).

Without this, today we must manually import it.

This would allow it to work similar to how ng g s data -m some.module and ng g c customer -mother.module work today

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions