Feature: Either add scope to attributes that are passed to templateUrl function or preprocess attributes based on scope parameters

[spaceribs]

As you can see in the following plunker, you cannot access a scoped value within the directive's templateUrl. All attributes are passed uncompiled, and there is no way to access the scope within this context. I have a workaround with a lot of dependencies injected within the link function of that directive (showing how it should work).

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!

[filiptc]

+1 to this feature request. Not being able to access scope from templateURL function nor getting scope-preprocessed attributes forces workaround use of link and manual $http loading of templates.

[spaceribs]

Yes, please reopen this issue, it is still a missing feature.

[gregaton]

This is still a missing feature.
Please reopen.

[localpcguy]

This should be reopened. Either scope should be accessible as an attribute of the templateUrl function or scope bindings should be evaluated before attributes are passed to the function

[spaceribs]

I think this is a similar issue to issue #1039, and essentially it boils down to the compileTemplateUrl being called before the scope is available. Please merge these issues.

[shox]

I'm struggling with this issue from two days, please reopen this issue.

[jimmywarting]

dosen't ngInclude works for you?
Perhaps something like this example

[spaceribs]

@jimmywarting Yes you could do something like this, but that requires 2 compiles when only one should be needed. A directive should be self contained, not requiring other core directives to be used alongside it. Technically you could do the same thing by setting the templateUrl to '/views/loader.html' with:

<div ng-include="'/views/'+model.type+'-type.html'"></div>

but that now requires 2 ajax calls and 2 child scopes when you only really needed one.

Being able to grab a template type from the scope and apply it to the templateUrl dynamically is a long sought after feature that directives could benefit from, but I believe it's a "chicken before the egg" issue looking at the code myself, and would require a major revamp in the order of operations for compiling a directive.