Why not put the todos in scope so no need to use vm
On Wednesday, June 1, 2016 at 5:37:02 PM UTC+3, Yonk wrote:
>
> Hello I'm Yonk. I'm an incredibly curious newbie. Please if anyone has
> time can you explain to me if these refactors to the patterns of angular
> are good? I really enjoy things like the practice of programming and try
> to avoid acronyms at all cost. Is there a reason why you wouldn't go my
> route and the acronyms are the absolute defacto standard. I'm assuming
> it's just a style choice of the team but I'd like learn more about things i
> know little about =)
>
> <li ng-repeat="todo in vm.todos">
> <h4>{{ todo.title }}</h4>
> </li>
>
> <li (( repeat='todo in vm.todos' ))>
> <h4>{{ todo.title }}</h4>
> </li>
>
> <li (( repeat='todo in ^.todos' ))>
> <h4>{{ todo.title }}</h4>
> </li>
>
>
>
> Would these refactors even be possible? I feel if vm is an implied
> variable maybe make it a special thing like a caret. then the caret can be
> the VMO View Model Object =) Also everything inside the parenthesis would
> look first for a native directive then for possible custom directives.
>
> I would appreciate any thoughts and opinions if this is a good refactor or
> a bad refactor. There's no such thing as criticism only brain storming.
>
> <3
>
--
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 https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
