Skip to content

Instantly share code, notes, and snippets.

@vades

vades/Angular-Architecture.md

Last active May 22, 2019 13:41
Show Gist options
  • Save vades/051bd64709285060074760bce2e3c553 to your computer and use it in GitHub Desktop.
Save vades/051bd64709285060074760bce2e3c553 to your computer and use it in GitHub Desktop.
Download ZIP
How to structure Angular project
Raw
Angular-Architecture.md

How to structure Angular project

A good guideline to follow is to split Angular application into at least three modules:

  1. Core.
  2. Features.
  3. Shared.

Core

All services which have to have one instance per application should be implemented here.

Features

A feature module delivers a cohesive set of functionality focused on a specific application.

  • Feature modules should only import services from CoreModule.
  • These modules don’t depend on any other features just on services provided by CoreModule and components provided by SharedModule.

Shared

All components and pipes should be implemented here.

  • These components don’t import and inject services from core or other features.
  • They should receive all data though attributes in the view.
  • Shared modules doesn’t have any dependency to the rest of the application.

Sources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment