I'm using the ngInclude
directive to load HTML fragments. Now I'm looking for the best way to pass a dynamic URL. I know I can create the URL with string concatenation:
<ng-include src="'/foo/' + fooId + '/bar/' + barId + '/baz/' + bazId"></ng-include>
In my eyes this is a bit ugly.
ngHref
and ngSrc
for example, accept URLs containing {{}}
markup. IMHO this syntax is much cleaner:
<img ng-src="/foo/{{fooId}}/bar/{{barId}}/baz/{{bazId}}"/>
<a ng-href="/foo/{{fooId}}/bar/{{barId}}/baz/{{bazId}}"/>
Is there a better way to pass dynamic URLs to ngInclude?
Not sure if this is "better" or not, but you could create a function on your scope to encapsulate this.
app.controller("MyCtrl", function($scope) {
$scope.fooId = "123";
$scope.barId = "abc";
$scope.bazId = "abc";
$scope.templateUrl = function() {
return "/foo/"+ $scope.fooId +"/bar/"+ $scope.barId +"/baz/"+ $scope.bazId;
}
});
Then you would use it like so...
<div ng-controller="MyCtrl">
<ng-include src="templateUrl()"></ng-include>
</div>
Here's a live example of this type of thing: http://plnkr.co/edit/Lu3icqPgg1dpNCj6a3Dn?p=preview
@jessegavin is better use this code
<ng-include ng-init="tmplUrl = templateUrl();" src="tmplUrl"></ng-include>
if you will use this way
<ng-include src="templateUrl()"></ng-include>
templateUrl calls a few times. (3 times). try console.log. i think because of $scope varibles
$scope.templateUrl = function() {
var url = "/foo/"+ $scope.fooId +"/bar/"+ $scope.barId +"/baz/"+ $scope.bazId;
console.log(url);
return url;
}