Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Folder Structure does follow Angular’s best practices #25

Open
KevinStarWars opened this issue Sep 18, 2019 · 0 comments
Open

Folder Structure does follow Angular’s best practices #25

KevinStarWars opened this issue Sep 18, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@KevinStarWars
Copy link
Contributor

Angular's best practices (https://angular.io/guide/styleguide) give a clear indication of how an Angular Project needs to be structured. Therefore the style guide suggests four main design patterns:

  1. All feature areas are in their own folder, with their own NgModule.
  2. All distinct features are in their own folder, with their own NgModule. The feature folder is placed inside the respective feature area folder.
  3. Create a folder module named Shared Module in a shared folder. Commonly used components, directives and pipes are placed inside SharedModule.
  4. Create a core folder including a CoreModule. Services and Modules, which are used system-wide are placed inside the core folder.

All four design patterns are not well executed inside the ngRx-template. Therefore the project needs to be restructured following these design patterns.

@KevinStarWars KevinStarWars added the enhancement New feature or request label Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant