Paths should follow the styleguide

[hansl]

Following the Houston app demo;

• The directory structure need to be only including routes (not components, services or pipes). Components, services and pipes need to be in an _ directory inside the route
  The following commands need to be changes (feel free to check those that are solved):
  • new: simply a matter of updating the scaffold.
  • generate:
    • component/service/pipe: need to be added to an _ directory in the route specified. For example, ng generate component foo/bar/blah should be generated in the directory foo/bar/_/blah. If the _ is included then we don't need to add it (an _ route would be invalid here).
    • route: the scaffold need to include an empty _ directory under the route itself.
• Adding an index.ts file to all scaffolds that export the component/route/service/pipe of that directory.

I think that's it for this.

[filipesilva]

We should put off merging this this PR until the official style guide is in. Otherwise users will have no idea nor guidance as to how the structure is meant to be used.

[hansl]

That is the official styleguide though. The document is going to adhere to this, not the other way around.

[filipesilva]

The repo is not a document. We can't direct users to the repo for insights on style guide issues.

We need a document that users can read and understand before we change the CLI to use it.

[Brocco]

At the current state of the project (pre-alpha) I think we can make changes without documentation in place. Especially given our milestone goals.

[mattcarp]

Hi @hansl. Would you have a link to the repo mentioned?

[Brocco]

Fixed via #427

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