Skip to content

Commit 4ed8dc8

Browse files
dgp1130thePunderWoman
dgp1130
authored and
thePunderWoman
committed
docs: remove Ivy-specific guides (#43860)
Ivy is the only supported rendering engine in v13, so there is no need to document the concept. Everything in Angular is Ivy. This starts the removal process by deleting Ivy-specific guides and references to them. It also updates the glossary to be more clear that Ivy is the current rendering engine while View Engine is simply a historical note. This does not attempt to fully remove all references to "Ivy" or "View Engine", that will likely be a more involved clean up process. PR Close #43860
1 parent 45e4e60 commit 4ed8dc8

File tree

11 files changed

+13
-788
lines changed

11 files changed

+13
-788
lines changed

‎aio/content/guide/angular-compiler-options.md‎

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ These message formats have a number of issues, such as whitespace handling and r
7474
The new message format is more resilient to whitespace changes, is the same across all translation file formats, and can be generated directly from calls to `$localize`.
7575
This allows `$localize` messages in application code to use the same ID as identical `i18n` messages in component templates.
7676

77-
### `enableIvy`
78-
79-
Enables the [Ivy](guide/ivy) compilation and rendering pipeline. Default is `true`, as of version 9. In version 9, you can [opt out of Ivy](guide/ivy#opting-out-of-angular-ivy) to continue using the previous compiler, View Engine.
80-
81-
For library projects generated with the CLI, the production configuration default is `false` in version 9.
82-
8377
### `enableResourceInlining`
8478

8579
When `true`, replaces the `templateUrl` and `styleUrls` property in all `@Component` decorators with inlined contents in `template` and `styles` properties.
@@ -180,7 +174,7 @@ When you use the CLI command `ng new --strict`, it is set to `true` in the gener
180174

181175
### `strictTemplates`
182176

183-
When `true`, enables [strict template type checking](guide/template-typecheck#strict-mode). Strict mode is only available when using [Ivy](guide/ivy) (Angular version 9 and later).
177+
When `true`, enables [strict template type checking](guide/template-typecheck#strict-mode).
184178

185179
Additional strictness flags allow you to enable and disable specific types of strict template type checking. See [troubleshooting template errors](guide/template-typecheck#troubleshooting-template-errors).
186180

‎aio/content/guide/aot-compiler.md‎

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -551,18 +551,6 @@ In the template type-checking phase, the Angular template compiler uses the Type
551551
Enable this phase explicitly by adding the compiler option `"fullTemplateTypeCheck"` in the `"angularCompilerOptions"` of the project's TypeScript configuration file
552552
(see [Angular Compiler Options](guide/angular-compiler-options)).
553553

554-
<div class="alert is-helpful">
555-
556-
In [Angular Ivy](guide/ivy), the template type checker has been completely rewritten to be more capable as well as stricter, meaning it can catch a variety of new errors that the previous type checker would not detect.
557-
558-
As a result, templates that previously compiled under View Engine can fail type checking under Ivy. This can happen because Ivy's stricter checking catches genuine errors, or because application code is not typed correctly, or because the application uses libraries in which typings are inaccurate or not specific enough.
559-
560-
This stricter type checking is not enabled by default in version 9, but can be enabled by setting the `strictTemplates` configuration option.
561-
562-
For more information about type-checking options, and about improvements to template type checking in version 9 and above, see [Template type checking](guide/template-typecheck).
563-
564-
</div>
565-
566554
Template validation produces error messages when a type error is detected in a template binding
567555
expression, similar to how type errors are reported by the TypeScript compiler against code in a `.ts`
568556
file.

‎aio/content/guide/entry-components.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,9 @@
22

33
<div class="alert is-helpful">
44

5-
Entry components have been deprecated with the [Ivy rendering engine](guide/ivy).
6-
For more information, see [entryComponents deprecation](guide/deprecations#entrycomponents-and-analyze_for_entry_components-no-longer-required) in the [Deprecated APIs and features](guide/deprecations).
5+
Entry components are deprecated, for more information, see
6+
[entryComponents deprecation](guide/deprecations#entrycomponents-and-analyze_for_entry_components-no-longer-required)
7+
in the [Deprecated APIs and features](guide/deprecations).
78

89
</div>
910

‎aio/content/guide/glossary.md‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -495,10 +495,9 @@ Read more in the [Interpolation](guide/interpolation) guide.
495495

496496
## Ivy
497497

498-
Ivy is the code name for Angular's [next-generation compilation and rendering pipeline](https://blog.angular.io/a-plan-for-version-8-0-and-ivy-b3318dfc19f7).
499-
With the version 9 release of Angular, the new compiler and runtime instructions are used by default instead of the older compiler and runtime, known as [View Engine](#ve).
500-
501-
See [Angular Ivy](guide/ivy).
498+
Ivy is the historical code name for Angular's current
499+
[compilation and rendering pipeline](https://blog.angular.io/a-plan-for-version-8-0-and-ivy-b3318dfc19f7).
500+
It is now the only supported engine, so everything uses Ivy.
502501

503502

504503
{@a J}
@@ -1061,7 +1060,9 @@ View hierarchies can be loaded and unloaded dynamically as the user navigates th
10611060

10621061
## View Engine
10631062

1064-
The compilation and rendering pipeline used by Angular before version 9. Compare [Ivy](#ivy).
1063+
A previous compilation and rendering pipeline used by Angular. It has since been replaced by
1064+
[Ivy](#ivy) and is no longer in use. View Engine was deprecated in version 9 and removed in version
1065+
13.
10651066

10661067

10671068
{@a view-tree}

‎aio/content/guide/i18n-common-merge.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
To merge the completed translations into your project, complete the following actions
44

55
1. Use the [Angular CLI][AioCliMain] to build a copy of the distributable files of your project
6-
1. Use the `"localize"` option to replace all of the i18n messages with the valid translations and build a localized variant application.
6+
1. Use the `"localize"` option to replace all of the i18n messages with the valid translations and build a localized variant application.
77
A variant application is a complete a copy of the distributable files of your application translated for a single locale.
88

99
After you merge the translations, serve each distributable copy of the application using server-side language detection or different subdirectories.
@@ -195,8 +195,6 @@ Compile once, then translate for each locale.
195195

196196
[AioGuideI18nCommonTranslationFilesChangeTheSourceLanguageFileFormat]: guide/i18n-common-translation-files#change-the-source-language-file-format "Change the source language file format - Work with translation files | Angular"
197197

198-
[AioGuideIvyOptingOutOfIvyInVersion9]: guide/ivy#opting-out-of-ivy-in-version-9 "Opting out of Ivy in version 9 - Angular Ivy | Angular"
199-
200198
[AioGuideWorkspaceConfig]: guide/workspace-config "Angular workspace configuration | Angular"
201199

202200
<!-- external links -->

0 commit comments

Comments
 (0)