Paul Gschwendtner 8de3c20e50 fix(ivy): do not reset view dirty state in check no changes mode (#34495) ... Unlike in View Engine, we currently reset the dirty state of components in the check no changes change detection cycle. This means that components cannot be marked as dirty from view lifecycle hooks because the dirty state is reset and the lifecycle hooks do not run in the check no changes CD cycle. PR Close #34495		2020-01-13 09:43:16 -08:00
..
schematics	Revert "build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34589)" (#34730)	2020-01-10 14:12:15 -08:00
src	fix(ivy): do not reset view dirty state in check no changes mode (#34495)	2020-01-13 09:43:16 -08:00
test	fix(ivy): do not reset view dirty state in check no changes mode (#34495)	2020-01-13 09:43:16 -08:00
testing	fix(ivy): TestBed not unwrapping imports array function when overriding provider (#34629)	2020-01-06 11:38:02 -08:00
BUILD.bazel	Revert "build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34589)" (#34730)	2020-01-10 14:12:15 -08:00
PACKAGE.md	docs: add package doc files (#26047)	2018-10-05 15:42:14 -07:00
global.ts	feat(docs-infra): add the ability to expose globals (#34237)	2019-12-06 10:58:09 -08:00
index.ts	refactor: move angular source to /packages rather than modules/@angular	2017-03-08 16:29:27 -08:00
package.json	build: set up all packages to publish via wombot proxy (#33747)	2019-11-13 11:34:33 -08:00
public_api.ts	build: publish tree of files rather than FESMs (#18541)	2017-08-31 15:34:50 -07:00