Hacker News Reader

Comment by alexmic | Hacker News Reader

Did the limitation of having only one ng-view affect your project at all? I'm embarking on a new project using Angular and there are mixed opinions on the web. People that were shouting against it have come back saying that it's actually not so bad [1].

[1] https://groups.google.com/forum/?fromgroups=#!topic/angular/...

View on HN

(Tech lead @ CropUp)

In the first iteration, we thought multiple ngViews would have been useful, but it didn't prevent us from achieving the design we wanted. You can use ngInclude to accomplish a similar effect, if you don't need the routing.

AngularUI seems to have a solution for nested views/routing here (https://github.com/angular-ui/ui-router). Although, I would think about your routes and the pieces of your web application and rethink whether you really need ngView. Using ngIncludes for pieces you want to reuse might make more sense.

edit: for clarity

It sure makes more sense, but you need to write boilerplate code to map URL state to ng-include changes/updates. It would be nice if it was out of the box.

I don't know the details of your app but maybe you should consider using ngView in the outer most container, then everything inside the container can pick the appropriate template via ngInclude. That's the path we took in our first iteration, this current iteration actually doesn't need nested/multiple ngViews.

ng-view is not simply a view (I think the name confuses most users), if you want multiple ng-views you will probably need more routers. Maybe there are some use cases for it, I just can't really think of one. You will pretty much split your application in N.

You really really really really want to keep those kind of things in directives.

Anyway, I read about it sometime ago on a github issue it is 'planned'.

Reply on news.ycombinator.com