Just checked it again and apparently the form example has since been fixed to allow the usage of main.form.email.$valid.
On Wednesday, December 18, 2013 2:29:05 AM UTC+8, Kay wrote: > > The "controller-as" syntax raised some inconsistencies to the framework's > design decisions which, I believe, need to be addressed or at least > clarified. > > One of the issues is that special models that are generated by the > framework, eg. item in ng-repeat="item in main.items", or > form.email.$valid in <form name="form"><input name="email" > type="email"></form> are still being put under $scope regardless of the > "controller-as" > syntax, so conceptually there is now two competing model containers storing > interrelated information that should really be integrated as a single > whole. However you also probably won't wanna hook these special models > under main (or other controller instance alias) because ng-repeat="main.item > in main.items" or main.form.email.$valid are just way too verbose and > stupid. > > It seems to me that while the "controller-as" syntax (btw, we need a > better name than that to refer to this feature...) solves a certain > problem, ie. the primitive type binding issue, it's hardly a beneficial > addition to the integrity of the framework, and is probably introduced > majorly for the sake of AngularDart or some Google coding styles. > -- 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/groups/opt_out.
