aboutsummaryrefslogtreecommitdiffstats
path: root/test/ng/directive
AgeCommit message (Collapse)Author
2012-04-03refactor(ngView): remove extra $watch, refactor one ugly testVojta Jina
2012-04-03fix(ngInclude): fire $includeContentLoaded on proper (child) scopeVojta Jina
2012-04-03refactor(ngInclude): remove scope attributeVojta Jina
The purpose of allowing the scope to be specified was to enable the $route service to work together with ngInclude. However the functionality of creating scopes was in the recent past moved from the $route service to the ngView directive, so currently there is no valid use case for specifying the scope for ngInclude. In fact, allowing the scope to be defined can under certain circumstances lead to memory leaks. Breaks ngInclude does not have scope attribute anymore.
2012-04-03feat(ngModel): update model on each key stroke (revert ngModelInstant)Vojta Jina
It turns out that listening only on "blur" event is not sufficient in many scenarios, especially when you use form validation you always had to use ngModelnstant e.g. if you want to disable a button based on valid/invalid form. The feedback we got from our apps as well as external apps is that the ngModelInstant should be the default. In the future we might provide alternative ways of suppressing updates on each key stroke, but it's not going to be the default behavior. Apps already using the ngModelInstant can safely remove it from their templates. Input fields without ngModelInstant directive will start propagating the input changes into the model on each key stroke.
2012-03-29fix(ngValue): bind properly inside ng-repeatVojta Jina
2012-03-28chore(module): move files around in preparation for more modulesMisko Hevery