A toy application written as a personal reference / experiment using some angular 1.x design patterns.

• Clone this repo
• Run npm install, to install dependencies (requires Node.js)
• Run grunt to start the server
• Go to localhost:3000 in your favorite web browser. That's it!

I tried my best to stick to john_papa's Angular Style Guide.

A nice way to handle interacting with models in controllers.

These factories create multiple new instances (not just the singleton that an Angular factory creates for us) of our models. We can then attach methods to these objects that encapsulate the application-specific logic that may be attached to them, such as validation or model persistance.

So, for example, instead of having to define the behavior for saving a model to the database inside the controller, we can attach a save() method to the model itself, and in the controller simply call model.save().

These services exposes an API to your factories for sending and receiving data from the server. In order to preserve separation of concerns, it is a good idea to keep this abstracted away from your factories.

Sources:

• AngularJS: Understanding Design Patterns (StackOverflow) (see izhaki's answer)
• Non-Singleton Services in Angular (StackOverflow)

A cool, react-esque way of rethinking angular controllers, especially with Angular 2 in mind.

A component is an Angular directive with a named controller attached to it. Its data and behavior is provided through its isolate scope by the container it resides in. This allows the component's controller to focus solely on providing a "View Model" to the DOM.

Another benefit of using components is inter-component communication; since the data passed through the isolate scope is two-way bound, any other component within the same container will see changes made to the data in real time.

Containers are Angular controllers that contain components, provide those components with data, and mediate inter-component communication. As stated above, containers perform data retrieval by interacting with factories and passing the data produced along to their components.

Note that while the containers used in this app only exist one-per-page, there could be scenarios in which multiple containers exist on a page, or when containers exist within other containers or even components. In such scenarios it might make sense to attach your containers to directives.

Sources:

• How I've Improved My Angular Apps By Banning ng-controller (Article)
• Container-Component Pattern in Angular 1 (Article)