5 commits

Author	SHA1	Message	Date
Igor Minar	0f89383d98	chore(tests): rename all directive names to the normalized form	2012-04-09 11:48:54 -07:00
Vojta Jina	8fe4295a06	refactor(ngInclude): correct the tests	2012-04-04 14:58:07 -07:00
Vojta Jina	199ac26986	fix(ngInclude): fire $includeContentLoaded on proper (child) scope	2012-04-03 10:10:44 -07:00
Vojta Jina	5f70d615a5	refactor(ngInclude): remove scope attribute ... 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-03 10:10:44 -07:00
Misko Hevery	2430f52bb9	chore(module): move files around in preparation for more modules	2012-03-28 11:16:35 -07:00

Renamed from test/directive/ngIncludeSpec.js (Browse further)