| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2012-05-04 | chore(docs): re-skin main documentation | Misko Hevery | |
| 2012-04-10 | chore(*): remove dead code and fix code style issues | Igor Minar | |
| 2012-04-09 | fix(docs): change all directive references to use the normalized names | Igor Minar | |
| 2012-04-03 | feat(ngInclude): allow ngInclude on css class | Vojta Jina | |
| And make it terminal so that it does not compile its content, which would cause leaks. | |||
| 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 | |
 |
index : angular.js | |
| aboutsummaryrefslogtreecommitdiffstats |