feat(blueprints router): add the router

[cironunes]

WIP to address #66

How far should we go with the implementation? I've tried to do as few as possible, but it would be nice to have at least one more route maybe showing the usage of RouteParams. WDYT?

[Brocco]

I like the idea of providing something with routing as part of the new, but am concerned that users may get annoyed of having to go in and delete a hello component every time they generate a new project.

Possibly adding the idea via a command arg to either turn that generation on or off?

[cironunes]

+1 to adding via command arg, or maybe prompting the user?

[Brocco]

Maybe both (arg + prompt) meaning we can prompt the user if the arg isn't specified? (not sure how I feel about it, but open for discussion)

Also, as for implementation, what about instead of adding the component to the ng2/new blueprint, how about calling the ng generate component hello from within to alleviate the maintenance on multiple blueprints?

[cironunes]

Also, as for implementation, what about instead of adding the component to the ng2/new blueprint, how about calling the ng generate component hello from within to alleviate the maintenance on multiple blueprints?

Good catch. Will do

[cironunes]

it should use PathLocationStrategy

[filipesilva]

@cironunes @Brocco are you happy enough with the implementation at #139?

If so, I think this one can be closed.

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