AngularJS: multiples views using same controller best practice

Question

I've made an app with 3 slightly different views which use the same logic, so each one uses the same controller, but have different json data. Everything is working fine, but I was wondering if it is AngularJS best practice to do so ? When routes change, does the view replaced uses the same instance of the controller, or does it instantiate a new controller ?

Thanx.

In my small experience, each time a view changes, its controller was reloaded. I'm using ui-router, so maybe AngularJs basic routes don't have the same behavior. You can put "console.log" in your controller to detect this. — Neozaru
– Neozaru, Commented Dec 10, 2013 at 15:55
I wondered the same about here is some helpful info Angular Best Practices — Dalorzo
– Dalorzo, Commented May 17, 2014 at 22:43

Phil Sandler · Accepted Answer · 2013-12-10 16:01:20Z

1

A new controller is created each time a view is loaded--controllers are transient in this sense. If state needs to be maintained, you should use a service or factory.

I personally will share controllers between different variations of the same view. In a general sense, if the controller represents the same logic (or abstraction) in relation to the view, I see no reason not to re-use it.

answered Dec 10, 2013 at 16:01

Phil Sandler

28.1k21 gold badges88 silver badges153 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

AngularJS: multiples views using same controller best practice

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related