Think you have misunderstood the question, we don't have any issues... Our
solution works, but according to the documentation, that is really a hack...
Seeing as they have written what they have regarding the ng-init approach,
I am just wondering what they think the correct approach is.
Maybe the use of ng-init is fine, but we are just touching base with a use
case they had not thought about. In that case the documentation might be a
bit to restrictive, and could be loosened up...
On Tuesday, July 15, 2014 11:25:55 AM UTC+2, Sander Elias wrote:
>
> Hi Jens,
>
> I’m not on the core team, but I think I have a simple solution to your
> problem.
>
> app.directive('appInit', ['$parse', function ($parse) {
> return {
> restrict: 'A',
> link: function (scope, elm, attr) {
> $parse(attr.appInit)(scope);
> }
> };
> }]);
>
> to be used as:
>
> <div ng-controller='appController as app' app-init="app.initialize(42,
> 'spock')">
>
> You can see it in action here:
> http://plnkr.co/edit/zKBgyLSGQ0el2WUQHE3F?p=preview
>
> Does that solve your issue?
>
> Regards
> Sander
>
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
