Internal Url inconsistency with ng-href and location.path

[mark0978]

I find myself having to write urls in two different manners

ng-href="#something" and location.path("something")

Since I have a urlService in my app to generate urls for various things, this means I have to scatter .substring(1) thruout my code to deal with location.path() like this location.path(urlService.createFoo(args).substring(1)) so that I can use

    <a ng-href=urlService(createFoo(args))>Link text</a>

It would be nice if they both took the same string and since ng-href has to have the # so that you could actually leave the page with a /something, it makes sense to have location.path ignore the first character if it is a '#' character

[IgorMinar]

yes. this is wrong. ui-route has fixed this already and our new router will also provide a way to generate urls so that you don't have to worry about this.

I'm not sure if we are going to fix this in 1.2/1.3 though as that would be a big breaking change. We'll discuss it though.