AngularJS -> UI router, where to define controller

Question

One can define controller for the state in ui router as controller: 'MainController', but also this can be omitted, and instead controller can be defined in view (template url) as ng-controller="MainController", what is the better practice?

Robin-Hoodie · Accepted Answer · 2015-05-03 08:11:17Z

1

The better practice is to define the controller in the provider configuration (this also works with the core $routeProvider btw). It's best to keep your view as 'clean' as possible.

As @JBNizet added, this is also the only way for the router to inject the resolved dependencies into the controller (see the resolve property that you can pass into your route/state config)

edited May 3, 2015 at 8:11

answered May 3, 2015 at 7:43

Robin-Hoodie

4,9944 gold badges33 silver badges65 bronze badges

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

8 Comments

JB Nizet Over a year ago

But more importantly, that's the only way for the router to injected the resolved dependencies to the controller.

Robin-Hoodie Over a year ago

Correct, I'll add it to to my answer

Drumbeg Over a year ago

I have an Angular app in which my controller is defined by my routeProvider, however, in the associated view, I have references to scope member variables so the view still feels tightly coupled to my controller. Am I doing something wrong?

Robin-Hoodie Over a year ago

@Drumbeg Referencing to scope member variables isn't wrong no

Drumbeg Over a year ago

Cheers @NexusDuck. I realised a while back that my view is actually referencing a model, not a controller, which is more in line with how I picture MVC to work.

|

Collectives™ on Stack Overflow

AngularJS -> UI router, where to define controller

1 Answer 1

8 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

8 Comments

Your Answer

Sign up or log in

Post as a guest

Related