| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2012-04-09 | chore(tests): rename all directive names to the normalized form | Igor Minar | |
| 2012-04-04 | refactor(ngInclude): correct the tests | Vojta Jina | |
| 2012-04-03 | fix(ngInclude): fire $includeContentLoaded on proper (child) scope | Vojta Jina | |
| 2012-04-03 | refactor(ngInclude): remove scope attribute | Vojta 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-28 | chore(module): move files around in preparation for more modules | Misko Hevery | |
