templateUrl: relative to app base or relative to their states' urls?

[laurelnaiad]

I wonder whether having templateUrls be interpreted relative to the state's url is such a good idea. I was really confused that when I was in a state with a url '/x/y' and I specified a template 'myTempl.html' that the template was being sought at '/x/y/myTempl.html'. I would think that given the way states' urls could be pretty much anywhere, you'd want the templateUrls to be relative to the appbase instead of the state's url... I think this only appears in html5 mode (which makes sense).

I know there's changes in how angular treats app base in the works: angular/angular.js#2969 ...I wonder how they'll impact ui-router in general, if at all.

[ksperling]

Hm, I didn't realize they were... ui-router doesn't do anything to the template URLs one way or another, they just get passed to $templateFactory and from there to $http. Possibly there have been some changes to how $router loads templates as part of the upstream app base changes that should be merged into $templateFactory.

[laurelnaiad]

Based on that issue I linked, it seems like there's some question as to how url's for templates should be interpreted within the core team.

I don't think the appBase changes in that PR are in anything other than Igor Minar's repository, yet.

Unless there is some reason to try to influence how that proceeds, maybe it's best to wait and see how it shakes out.

[nateabele]

Since I'm guessing this is probably a <base />-related issue, can we close it? /cc @stu-salsbury

[laurelnaiad]

I think you can certainly control it with base. Thanks for cleaning up.