Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: adding a note on extra text interpolations and HTML tags in translations to Ivy guide #36029

Closed
wants to merge 4 commits into from
Closed

docs: adding a note on extra text interpolations and HTML tags in translations to Ivy guide #36029

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
da3f95b
docs: adding a note on extra text interpolations and HTML tags in tra…
AndrewKushnir Mar 11, 2020
909ccf9
fixup! docs: adding a note on extra text interpolations and HTML tags…
AndrewKushnir Mar 12, 2020
f1feaf9
fixup! docs: adding a note on extra text interpolations and HTML tags…
AndrewKushnir Mar 12, 2020
bdaad61
fixup! docs: adding a note on extra text interpolations and HTML tags…
AndrewKushnir Mar 17, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions aio/content/guide/ivy-compatibility.md
View file
Open in desktop
Expand Up @@ -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`).
Expand Down