aboutsummaryrefslogtreecommitdiffstats
path: root/test/ng/directive/ngIncludeSpec.js
AgeCommit message (Collapse)Author
2013-04-11fix(ngAnimate): prevent animation on initial page loadMisko Hevery
2013-04-11fix(ngAnimate): skip animation on first renderMatias Niemelàˆ
2013-04-02feat(ngAnimate): add support for animationMisko Hevery
2013-03-27feat(http): support request/response promise chainingSylvester Keil
myApp.factory('myAroundInterceptor', function($rootScope, $timeout) { return function(configPromise, responsePromise) { return { request: configPromise.then(function(config) { return config }); response: responsePromise.then(function(response) { return 'ha!'; } }); } myApp.config(function($httpProvider){ $httpProvider.aroundInterceptors.push('myAroundInterceptor'); });
2012-04-09chore(tests): rename all directive names to the normalized formIgor Minar
2012-04-04refactor(ngInclude): correct the testsVojta 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-03-28chore(module): move files around in preparation for more modulesMisko Hevery