This post is the 4th part of the “Angular 1.5 from the trenches” series, presenting the architecture of a component-oriented, “NG 2 ready” Angular 1.5 app we’re building.
module.component()method, introduced in Angular 1.5, may seem only a cosmetic addition, but the approach it promotes (and which we utilise to the full extent) results in a very different flavour of architecture than most of the “classic” Angular tutorials describe, so I hope you’ll learn a thing or two from our experience.
Table of Contents:
- Starting a new app in Angular 1.5 – does it make sense?
- Angular 1.5 app as a tree of components
- Communication between Angular 1.5 components (and with the API)
- A flexible Angular 1.5 project structure (the “fractal” architecture) [THIS POST]
- Writing Angular 1.5 project in ES6/ES2015 [COMING SOON]
- Unit testing Angular 1.5 components – a detailed guide [COMING SOON]
- E2E testing of component-oriented Angular 1.5 app [COMING SOON]
In the previous two articles, I’ve described the conceptual structure of an Angular 1.5 app: how to split an app into components and how components communicate. Now is the time to discuss the physical organization of a component-oriented app: the directory and file structure.