Isolated scope properties are not available in 'pre' link function when using 'templateUrl'

[dana-shalev]

I have an isolated directive which initializes its scope properties in the directive.scope attribute. In the pre link function I'm using those scope attributes.
However, I discovered that if i used 'templateUrl' instead of 'template' in my directive suddenly things stop working.

Apparently when I switched to use 'templateUrl' suddenly the 'pre' link function was called before the scope was initialized with the properties I defined in the directive.scope property.

Take a look at this plunker for an example:

• The message directive defines an isolated scope which has a message property taken from the attribute.
• When I print to the console the value of message from the pre function I get undefined (while in the post function I get the actual value).
• If I comment the templateUrl property and use template instead the pre function will also print the actual value.

[petebacondarwin]

I think you are right that this is a bug. Although template loading is asynchronous, it seems that the template has been loaded by the time the pre-link is called and but the set-up of the isolated scope has not occurred.
See this fiddle (http://plnkr.co/edit/n9EEOS1jm7aXIH37XfiF?p=preview) and put break points on the pre and post link functions as well as line 4265 of angular.js

[billstar]

I'm seeing a different, but related bug where scope vars prefixed with @ that are referenced in the link function, when $observed or not, are also undefined, only when using the templateUrl attribute.

[ryanzec]

Any update on this?

I mean I can use the template property but it would be a lot cleaner to be able to use a separate file and use the templateUrl.

[ivarni]

Having the same issue in 1.0.5 and 1.0.7

[derekrprice]

Experiencing this issue in 1.2.0rc1.

[trask]

This is fixed by #3927

[Narretz]

@petebacondarwin then it can be closed!