From 1aa5783a45677929a9811d1ce5ed50b2b950c82c Mon Sep 17 00:00:00 2001 From: Andrew Kushnir Date: Wed, 11 Mar 2020 16:17:55 -0700 Subject: [PATCH] docs: adding a note on extra text interpolations and HTML tags in translations to Ivy guide (#36029) This commit updates Ivy compatibility guide with additional note on extra text interpolations and HTML tags in translations. PR Close #36029 --- aio/content/guide/ivy-compatibility.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/aio/content/guide/ivy-compatibility.md b/aio/content/guide/ivy-compatibility.md index e8776cc946..2a7bfaa343 100644 --- a/aio/content/guide/ivy-compatibility.md +++ b/aio/content/guide/ivy-compatibility.md @@ -75,6 +75,10 @@ Please note that these constants are not meant to be used by 3rd party library o * 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). +* Adding text bindings into i18n translations that are not present in the source template itself will throw a runtime error (previously, including extra bindings in translations was permitted). + +* Extra HTML tags in i18n translations that are not present in the source template itself will be rendered as plain text (previously, these tags would render as HTML). + * 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}`). * `DebugElement.attributes` returns `undefined` for attributes that were added and then subsequently removed (previously, attributes added and later removed would have a value of `null`).