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.
Comments
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.