A lot of times, I have long forms that I divide into multiple tabbed sections. Each section is managed by it's own controller and there is a parent controller that manages the whole view. I use ui-router for dividing such sections into states.  Should I make a service instead of a controller to manage the all the sections but generally, I don't have business logic in their. It's mostly done for collection data altogether and passing  it to an API using ng-resource. I know
Is having a parent controller to manage a set of tabbed sections an anti-pattern for an angular application?
design patterns;javascript;anti patterns;angularjs