docs: changes AoT to AOT for consistency (#35112)

PR Close #35112
This commit is contained in:
Sonu Kapoor 2020-02-02 20:49:28 -05:00 committed by Miško Hevery
parent 991e665fba
commit 7fb66eca25
15 changed files with 24 additions and 24 deletions

View File

@ -1,6 +1,6 @@
# Angular compiler options # Angular compiler options
When you use [AoT compilation](guide/aot-compiler), you can control how your application is compiled by specifying *template* compiler options in the `tsconfig.json` [TypeScript configuration file](guide/typescript-configuration). When you use [AOT compilation](guide/aot-compiler), you can control how your application is compiled by specifying *template* compiler options in the `tsconfig.json` [TypeScript configuration file](guide/typescript-configuration).
The template options object, `angularCompilerOptions`, is a sibling to the `compilerOptions` object that supplies standard options to the TypeScript compiler. The template options object, `angularCompilerOptions`, is a sibling to the `compilerOptions` object that supplies standard options to the TypeScript compiler.
@ -21,7 +21,7 @@ The template options object, `angularCompilerOptions`, is a sibling to the `comp
{@a tsconfig-extends} {@a tsconfig-extends}
## Configuration inheritance with extends ## Configuration inheritance with extends
Like the TypeScript compiler, The Angular AoT compiler also supports `extends` in the `angularCompilerOptions` section of the TypeScript configuration file, `tsconfig.json`. Like the TypeScript compiler, The Angular AOT compiler also supports `extends` in the `angularCompilerOptions` section of the TypeScript configuration file, `tsconfig.json`.
The `extends` property is at the top level, parallel to `compilerOptions` and `angularCompilerOptions`. The `extends` property is at the top level, parallel to `compilerOptions` and `angularCompilerOptions`.
A TypeScript configuration can inherit settings from another file using the `extends` property. A TypeScript configuration can inherit settings from another file using the `extends` property.
@ -48,7 +48,7 @@ For more information, see the [TypeScript Handbook](https://www.typescriptlang.o
## Template options ## Template options
The following options are available for configuring the AoT template compiler. The following options are available for configuring the AOT template compiler.
### `allowEmptyCodegenFiles` ### `allowEmptyCodegenFiles`

View File

@ -518,7 +518,7 @@ const raw = String.raw`A tagged template ${expression} string`;
[`String.raw()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/raw) [`String.raw()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/raw)
is a _tag function_ native to JavaScript ES2015. is a _tag function_ native to JavaScript ES2015.
The AoT compiler does not support tagged template expressions; avoid them in metadata expressions. The AOT compiler does not support tagged template expressions; avoid them in metadata expressions.
<hr> <hr>

View File

@ -48,7 +48,7 @@ You can build, test, and lint the project with CLI commands:
</code-example> </code-example>
Notice that the configured builder for the project is different from the default builder for app projects. Notice that the configured builder for the project is different from the default builder for app projects.
This builder, among other things, ensures that the library is always built with the [AoT compiler](guide/aot-compiler), without the need to specify the `--prod` flag. This builder, among other things, ensures that the library is always built with the [AOT compiler](guide/aot-compiler), without the need to specify the `--prod` flag.
To make library code reusable you must define a public API for it. This "user layer" defines what is available to consumers of your library. A user of your library should be able to access public functionality (such as NgModules, service providers and general utility functions) through a single import path. To make library code reusable you must define a public API for it. This "user layer" defines what is available to consumers of your library. A user of your library should be able to access public functionality (such as NgModules, service providers and general utility functions) through a single import path.

View File

@ -26,7 +26,7 @@ The CLI schematic `@nguniversal/express-engine` performs the required steps, as
The [Tour of Heroes tutorial](tutorial) is the foundation for this walkthrough. The [Tour of Heroes tutorial](tutorial) is the foundation for this walkthrough.
In this example, the Angular CLI compiles and bundles the Universal version of the app with the In this example, the Angular CLI compiles and bundles the Universal version of the app with the
[Ahead-of-Time (AoT) compiler](guide/aot-compiler). [Ahead-of-Time (AOT) compiler](guide/aot-compiler).
A Node Express web server compiles HTML pages with Universal based on client requests. A Node Express web server compiles HTML pages with Universal based on client requests.
To create the server-side app module, `app.server.module.ts`, run the following CLI command. To create the server-side app module, `app.server.module.ts`, run the following CLI command.

View File

@ -594,23 +594,23 @@
"hidden": true "hidden": true
}, },
{ {
"title": "AoT Compiler", "title": "AOT Compiler",
"tooltip": "Understanding ahead-of-time compilation.", "tooltip": "Understanding ahead-of-time compilation.",
"children": [ "children": [
{ {
"url": "guide/aot-compiler", "url": "guide/aot-compiler",
"title": "Ahead-of-Time Compilation", "title": "Ahead-of-Time Compilation",
"tooltip": "Learn why and how to use the Ahead-of-Time (AoT) compiler." "tooltip": "Learn why and how to use the Ahead-of-Time (AOT) compiler."
}, },
{ {
"url": "guide/angular-compiler-options", "url": "guide/angular-compiler-options",
"title": "Angular Compiler Options", "title": "Angular Compiler Options",
"tooltip": "Configuring AoT compilation." "tooltip": "Configuring AOT compilation."
}, },
{ {
"url": "guide/aot-metadata-errors", "url": "guide/aot-metadata-errors",
"title": "AoT Metadata Errors", "title": "AOT Metadata Errors",
"tooltip": "Troubleshooting AoT compilation." "tooltip": "Troubleshooting AOT compilation."
}, },
{ {
"url": "guide/template-typecheck", "url": "guide/template-typecheck",

View File

@ -112,7 +112,7 @@ class ExampleZipper {
'!**/npm-debug.log', '!**/npm-debug.log',
'!**/example-config.json', '!**/example-config.json',
'!**/wallaby.js', '!**/wallaby.js',
// AoT related files // AOT related files
'!**/aot/**/*.*', '!**/aot/**/*.*',
'!**/*-aot.*' '!**/*-aot.*'
]; ];

View File

@ -169,7 +169,7 @@ Angular supports the following class decorators:
There are also a list of helper decorators that make the `@Component` and `@Directive` easier to use such as `@Input`, `@Output`, etc.; as well as a set of decorators that help `@Injectable` classes customize the injector such as `@Inject` and `@SkipSelf`. There are also a list of helper decorators that make the `@Component` and `@Directive` easier to use such as `@Input`, `@Output`, etc.; as well as a set of decorators that help `@Injectable` classes customize the injector such as `@Inject` and `@SkipSelf`.
Each of the class decorators can be thought of as class transformers that take the declared class and transform it, possibly using information from the helper decorators, to produce an Angular class. The JIT compiler performs this transformation at runtime. The AoT compiler performs this transformation at compile time. Each of the class decorators can be thought of as class transformers that take the declared class and transform it, possibly using information from the helper decorators, to produce an Angular class. The JIT compiler performs this transformation at runtime. The AOT compiler performs this transformation at compile time.
Each of the class decorators' class transformer creates a corresponding static member on the class that describes to the runtime how to use the class. For example, the `@Component` decorator creates a `ɵcmp` static member, `@Directive` create a `ɵdir`, etc. Internally, these class transformers are called a "Compiler". Most of the compilers are straight forward translations of the metadata specified in the decorator to the information provided in the corresponding definition and, therefore, do not require anything outside the source file to perform the conversion. However, the component, during production builds and for type checking a template require the module scope of the component which requires information from other files in the program. Each of the class decorators' class transformer creates a corresponding static member on the class that describes to the runtime how to use the class. For example, the `@Component` decorator creates a `ɵcmp` static member, `@Directive` create a `ɵdir`, etc. Internally, these class transformers are called a "Compiler". Most of the compilers are straight forward translations of the metadata specified in the decorator to the information provided in the corresponding definition and, therefore, do not require anything outside the source file to perform the conversion. However, the component, during production builds and for type checking a template require the module scope of the component which requires information from other files in the program.

View File

@ -52,7 +52,7 @@ A tool which "upgrades" `node_module` compiled with non-ivy `ngc` into ivy compl
## `@angular/core` changes ## `@angular/core` changes
The goal is for the `@Component` (and friends) to be the compiler of template. Since decorators are functions which execute during parsing of the `.js` file, the decorator can compile the template into Ivy. The AoT compiler's job is to remove the `@Component` and replace it with call to `ɵɵdefineComponent`. The goal is for the `@Component` (and friends) to be the compiler of template. Since decorators are functions which execute during parsing of the `.js` file, the decorator can compile the template into Ivy. The AOT compiler's job is to remove the `@Component` and replace it with call to `ɵɵdefineComponent`.
- ✅ `@angular/compiler` can patch itself onto: - ✅ `@angular/compiler` can patch itself onto:
- ✅ `@Injectable` - ✅ `@Injectable`

View File

@ -6,7 +6,7 @@
* found in the LICENSE file at https://angular.io/license * found in the LICENSE file at https://angular.io/license
*/ */
// #docplaster // #docplaster
import {Component, Directive, ElementRef, EventEmitter, Inject, Injectable, Injector, Input, NgModule, Output} from '@angular/core'; import {Component, Directive, ElementRef, EventEmitter, Injectable, Injector, Input, NgModule, Output} from '@angular/core';
import {BrowserModule} from '@angular/platform-browser'; import {BrowserModule} from '@angular/platform-browser';
import {platformBrowserDynamic} from '@angular/platform-browser-dynamic'; import {platformBrowserDynamic} from '@angular/platform-browser-dynamic';
import {UpgradeComponent, UpgradeModule, downgradeComponent, downgradeInjectable} from '@angular/upgrade/static'; import {UpgradeComponent, UpgradeModule, downgradeComponent, downgradeInjectable} from '@angular/upgrade/static';
@ -176,6 +176,6 @@ ng1AppModule.component('exampleApp', {
// #docregion bootstrap-ng2 // #docregion bootstrap-ng2
// We bootstrap the Angular module as we would do in a normal Angular app. // We bootstrap the Angular module as we would do in a normal Angular app.
// (We are using the dynamic browser platform as this example has not been compiled AoT.) // (We are using the dynamic browser platform as this example has not been compiled AOT.)
platformBrowserDynamic().bootstrapModule(Ng2AppModule); platformBrowserDynamic().bootstrapModule(Ng2AppModule);
// #enddocregion // #enddocregion

View File

@ -141,7 +141,7 @@ class MyLazyAngularModule {
const ng2BootstrapFn = (extraProviders: StaticProvider[]) => const ng2BootstrapFn = (extraProviders: StaticProvider[]) =>
platformBrowserDynamic(extraProviders).bootstrapModule(MyLazyAngularModule); platformBrowserDynamic(extraProviders).bootstrapModule(MyLazyAngularModule);
// #enddocregion // #enddocregion
// (We are using the dynamic browser platform, as this example has not been compiled AoT.) // (We are using the dynamic browser platform, as this example has not been compiled AOT.)
// #docregion basic-how-to // #docregion basic-how-to

View File

@ -21,7 +21,7 @@ import {LazyModuleRef, UpgradeAppType, controllerKey, getDowngradedModuleCount,
* A helper function that allows an Angular component to be used from AngularJS. * A helper function that allows an Angular component to be used from AngularJS.
* *
* *Part of the [upgrade/static](api?query=upgrade%2Fstatic) * *Part of the [upgrade/static](api?query=upgrade%2Fstatic)
* library for hybrid upgrade apps that support AoT compilation* * library for hybrid upgrade apps that support AOT compilation*
* *
* This helper function returns a factory function to be used for registering * This helper function returns a factory function to be used for registering
* an AngularJS wrapper directive for "downgrading" an Angular component. * an AngularJS wrapper directive for "downgrading" an Angular component.

View File

@ -17,7 +17,7 @@ import {getTypeName, isFunction, validateInjectionKey} from './util';
* A helper function to allow an Angular service to be accessible from AngularJS. * A helper function to allow an Angular service to be accessible from AngularJS.
* *
* *Part of the [upgrade/static](api?query=upgrade%2Fstatic) * *Part of the [upgrade/static](api?query=upgrade%2Fstatic)
* library for hybrid upgrade apps that support AoT compilation* * library for hybrid upgrade apps that support AOT compilation*
* *
* This helper function returns a factory function that provides access to the Angular * This helper function returns a factory function that provides access to the Angular
* service identified by the `token` parameter. * service identified by the `token` parameter.

View File

@ -27,7 +27,7 @@ let moduleUid = 0;
* instantiated. * instantiated.
* *
* *Part of the [upgrade/static](api?query=upgrade/static) library for hybrid upgrade apps that * *Part of the [upgrade/static](api?query=upgrade/static) library for hybrid upgrade apps that
* support AoT compilation.* * support AOT compilation.*
* *
* It allows loading/bootstrapping the Angular part of a hybrid application lazily and not having to * It allows loading/bootstrapping the Angular part of a hybrid application lazily and not having to
* pay the cost up-front. For example, you can have an AngularJS application that uses Angular for * pay the cost up-front. For example, you can have an AngularJS application that uses Angular for

View File

@ -33,7 +33,7 @@ class Bindings {
* A helper class that allows an AngularJS component to be used from Angular. * A helper class that allows an AngularJS component to be used from Angular.
* *
* *Part of the [upgrade/static](api?query=upgrade%2Fstatic) * *Part of the [upgrade/static](api?query=upgrade%2Fstatic)
* library for hybrid upgrade apps that support AoT compilation.* * library for hybrid upgrade apps that support AOT compilation.*
* *
* This helper class should be used as a base class for creating Angular directives * This helper class should be used as a base class for creating Angular directives
* that wrap AngularJS components that need to be "upgraded". * that wrap AngularJS components that need to be "upgraded".
@ -53,7 +53,7 @@ class Bindings {
* *
* In this example you can see that we must derive from the `UpgradeComponent` * In this example you can see that we must derive from the `UpgradeComponent`
* base class but also provide an {@link Directive `@Directive`} decorator. This is * base class but also provide an {@link Directive `@Directive`} decorator. This is
* because the AoT compiler requires that this information is statically available at * because the AOT compiler requires that this information is statically available at
* compile time. * compile time.
* *
* Note that we must do the following: * Note that we must do the following:

View File

@ -24,10 +24,10 @@ import {NgAdapterInjector} from './util';
* and has an instance method used to bootstrap the hybrid upgrade application. * and has an instance method used to bootstrap the hybrid upgrade application.
* *
* *Part of the [upgrade/static](api?query=upgrade/static) * *Part of the [upgrade/static](api?query=upgrade/static)
* library for hybrid upgrade apps that support AoT compilation* * library for hybrid upgrade apps that support AOT compilation*
* *
* The `upgrade/static` package contains helpers that allow AngularJS and Angular components * The `upgrade/static` package contains helpers that allow AngularJS and Angular components
* to be used together inside a hybrid upgrade application, which supports AoT compilation. * to be used together inside a hybrid upgrade application, which supports AOT compilation.
* *
* Specifically, the classes and functions in the `upgrade/static` module allow the following: * Specifically, the classes and functions in the `upgrade/static` module allow the following:
* *