Hi Jens, I know your solution works, and I understood your question. I just offered an alternate solution to the issue. The directive I offered does basicly the same thing as the ng-init directive, but it makes it clean by name what it's intended for. And it's under your complete control, so you can adapt it to anything you like. BTW there is no technical reason that forces you to stop ng-init. I think you have a good use-case for it. Its just not 100% blindly following docs/best practice.
There are still a whole lot of other solutions to your issue. You need to find one that suits you. 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.
