From c4fbd0bef7d2223ddd030790711ec0b40b051a24 Mon Sep 17 00:00:00 2001 From: Kara Erickson Date: Thu, 7 Nov 2019 16:28:59 -0800 Subject: [PATCH] docs: update ivy compatibility guide with latest changes (#33675) This commit removes one of the expected Ivy changes because we have decided to change the behavior to be more backwards-compatible. It also adds a bug fix that is technically breaking to the list of expected changes. PR Close #33675 --- aio/content/guide/ivy-compatibility.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/aio/content/guide/ivy-compatibility.md b/aio/content/guide/ivy-compatibility.md index 51332e95dc..c59e755c76 100644 --- a/aio/content/guide/ivy-compatibility.md +++ b/aio/content/guide/ivy-compatibility.md @@ -39,8 +39,6 @@ If the errors are gone, switch back to Ivy by removing the changes to the `tscon - If a token is injected with the `@Host` or `@Self` flag, the module injector is not searched for that token (previously, tokens marked with these flags would still search at the module level). -- If a template is declared in one view but inserted into a different view, change detection will occur for that template only when its insertion point is checked (previously, change detection would also run when its declaration point was checked). - - When accessing multiple local refs with the same name in template bindings, the first is matched (previously, the last instance was matched). - Directives that are used in an exported module (but not exported themselves) are exported publicly (previously, the compiler would automatically write a private, aliased export that it could use its global knowledge to resolve downstream). @@ -57,4 +55,6 @@ If the errors are gone, switch back to Ivy by removing the changes to the `tscon - Special injection tokens (e.g. `TemplateRef` or `ViewContainerRef`) return a new instance whenever they are requested (previously, instances of special tokens were shared if requested on the same node). This primarily affects tests that do identity comparison of these objects. -- ICU parsing happens at runtime, so only text, HTML tags and text bindings are allowed inside ICU cases (previously, directives were also permitted inside ICUs). \ No newline at end of file +- ICU parsing happens at runtime, so only text, HTML tags and text bindings are allowed inside ICU cases (previously, directives were also permitted inside ICUs). + +- Providers formatted as `{provide: X}` without a `useValue`, `useFactory`, `useExisting`, or `useClass` property are treated like `{provide: X, useClass: X}` (previously, it defaulted to `{provide: X, useValue: undefined}`). \ No newline at end of file