refactor(compiler): remove fullTemplateTypeCheck compiler option.

The option was deprecated back in v13. Users should use `strictTemplates: true`.

Author: JeanMeche

adev/src/content/reference/configs/angular-compiler-options.md

@@ -130,15 +130,6 @@ For example, if a library uses the `public_api.ts` file as the library index of
 The `flatModuleOutFile` option could then be set, for example, to `"index.js"`, which produces `index.d.ts` and `index.metadata.json` files.
 The `module` field of the library's `package.json` would be `"index.js"` and the `typings` field would be `"index.d.ts"`.
 
-### `fullTemplateTypeCheck`
-
-When `true`, the recommended value, enables the binding expression validation phase of the template compiler. This phase uses TypeScript to verify binding expressions.
-For more information, see [Template type checking](tools/cli/template-typecheck).
-
-Default is `false`, but when you use the Angular CLI command `ng new --strict`, it is set to `true` in the new project's configuration.
-
-IMPORTANT: The `fullTemplateTypeCheck` option has been deprecated in Angular 13 in favor of the `strictTemplates` family of compiler options.
-
 ### `generateCodeForLibraries`
 
 When `true`, creates factory files \(`.ngfactory.js` and `.ngstyle.js`\) for `.d.ts` files with a corresponding `.metadata.json` file. The default value is `true`.

adev/src/content/tools/cli/aot-compiler.md

@@ -369,7 +369,7 @@ And it does not interfere with the ES module's exported API.
 One of the Angular compiler's most helpful features is the ability to type-check expressions within templates, and catch any errors before they cause crashes at runtime.
 In the template type-checking phase, the Angular template compiler uses the TypeScript compiler to validate the binding expressions in templates.
 
-Enable this phase explicitly by adding the compiler option `"fullTemplateTypeCheck"` in the `"angularCompilerOptions"` of the project's TypeScript configuration file
+Enable this phase explicitly by adding the compiler option `"strictTemplates"` in the `"angularCompilerOptions"` of the project's TypeScript configuration file
 (see [Angular Compiler Options](reference/configs/angular-compiler-options)).
 
 Template validation produces error messages when a type error is detected in a template binding

goldens/public-api/compiler-cli/compiler_options.api.md

@@ -50,8 +50,6 @@ export interface LegacyNgcOptions {
     allowEmptyCodegenFiles?: boolean;
     flatModuleId?: string;
     flatModuleOutFile?: string;
-    // @deprecated
-    fullTemplateTypeCheck?: boolean;
     preserveWhitespaces?: boolean;
     strictInjectionParameters?: boolean;
 }

integration/cli-hello-world-ivy-i18n/tsconfig.json

@@ -14,7 +14,6 @@
     "lib": ["es2018", "dom"]
   },
   "angularCompilerOptions": {
-    "fullTemplateTypeCheck": true,
     "strictInjectionParameters": true
   }
 }

integration/cli-hello-world-lazy/tsconfig.json

@@ -14,7 +14,6 @@
     "lib": ["es2018", "dom"]
   },
   "angularCompilerOptions": {
-    "fullTemplateTypeCheck": true,
     "strictInjectionParameters": true
   }
 }

integration/defer/tsconfig.json

@@ -14,7 +14,6 @@
     "lib": ["es2018", "dom"]
   },
   "angularCompilerOptions": {
-    "fullTemplateTypeCheck": true,
     "strictInjectionParameters": true
   }
 }

integration/legacy-animations-async/tsconfig.json

@@ -15,7 +15,6 @@
     "lib": ["es2018", "dom"]
   },
   "angularCompilerOptions": {
-    "fullTemplateTypeCheck": true,
     "strictInjectionParameters": true
   }
 }

integration/legacy-animations/tsconfig.json

@@ -14,7 +14,6 @@
     "lib": ["es2018", "dom"]
   },
   "angularCompilerOptions": {
-    "fullTemplateTypeCheck": true,
     "strictInjectionParameters": true
   }
 }

integration/standalone-bootstrap/tsconfig.json

@@ -14,7 +14,6 @@
     "lib": ["es2018", "dom"]
   },
   "angularCompilerOptions": {
-    "fullTemplateTypeCheck": true,
     "strictInjectionParameters": true
   }
 }

packages/compiler-cli/src/ngtsc/core/api/src/public_options.ts

@@ -23,22 +23,6 @@ export interface LegacyNgcOptions {
    */
   allowEmptyCodegenFiles?: boolean;
 
-  /**
-   * Whether to type check the entire template.
-   *
-   * This flag currently controls a couple aspects of template type-checking, including
-   * whether embedded views are checked.
-   *
-   * For maximum type-checking, set this to `true`, and set `strictTemplates` to `true`.
-   *
-   * It is an error for this flag to be `false`, while `strictTemplates` is set to `true`.
-   *
-   * @deprecated The `fullTemplateTypeCheck` option has been superseded by the more granular
-   * `strictTemplates` family of compiler options. Usage of `fullTemplateTypeCheck` is therefore
-   * deprecated, `strictTemplates` and its related options should be used instead.
-   */
-  fullTemplateTypeCheck?: boolean;
-
   /**
    * Whether to generate a flat module index of the given name and the corresponding
    * flat module metadata. This option is intended to be used when creating flat
@@ -100,8 +84,6 @@ export interface TypeCheckingOptions {
   /**
    * If `true`, implies all template strictness flags below (unless individually disabled).
    *
-   * This flag is a superset of the deprecated `fullTemplateTypeCheck` option.
-   *
    * Defaults to `true`
    */
   strictTemplates?: boolean;
@@ -115,15 +97,15 @@ export interface TypeCheckingOptions {
    * directive or component is receiving the binding. If set to `true`, both sides of the assignment
    * are checked.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set.
+   * Defaults to `false`.
    */
   strictInputTypes?: boolean;
 
   /**
    * Whether to check if the input binding attempts to assign to a restricted field (readonly,
    * private, or protected) on the directive/component.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck", "strictTemplates" and/or
+   * Defaults to `false`, even if "strictTemplates" and/or
    * "strictInputTypes" is set. Note that if `strictInputTypes` is not set, or set to `false`, this
    * flag has no effect.
    *
@@ -140,7 +122,7 @@ export interface TypeCheckingOptions {
    * binding expressions are wrapped in a non-null assertion operator to effectively disable strict
    * null checks.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set. Note that if `strictInputTypes` is
+   * Defaults to `false`. Note that if `strictInputTypes` is
    * not set, or set to `false`, this flag has no effect.
    */
   strictNullInputTypes?: boolean;
@@ -154,7 +136,7 @@ export interface TypeCheckingOptions {
    * without a value, so with this flag set to `true`, an error would be reported. If set to
    * `false`, text attributes will never report an error.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set. Note that if `strictInputTypes` is
+   * Defaults to `false`. Note that if `strictInputTypes` is
    * not set, or set to `false`, this flag has no effect.
    */
   strictAttributeTypes?: boolean;
@@ -166,7 +148,7 @@ export interface TypeCheckingOptions {
    * then the return type of `a?.b` for example will be the same as the type of the ternary
    * expression `a != null ? a.b : a`.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set.
+   * Defaults to `false`.
    */
   strictSafeNavigationTypes?: boolean;
 
@@ -177,7 +159,7 @@ export interface TypeCheckingOptions {
    * determined by the type of `document.createElement` for the given DOM node. If set to `false`,
    * the type of `ref` for DOM nodes will be `any`.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set.
+   * Defaults to `false`.
    */
   strictDomLocalRefTypes?: boolean;
 
@@ -189,7 +171,7 @@ export interface TypeCheckingOptions {
    * `EventEmitter`/`Subject` of the output. If set to `false`, the `$event` variable will be of
    * type `any`.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set.
+   * Defaults to `false`.
    */
   strictOutputEventTypes?: boolean;
 
@@ -200,7 +182,7 @@ export interface TypeCheckingOptions {
    * `HTMLElementEventMap`, with a fallback to the native `Event` type. If set to `false`, the
    * `$event` variable will be of type `any`.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set.
+   * Defaults to `false`.
    */
   strictDomEventTypes?: boolean;
 
@@ -213,15 +195,15 @@ export interface TypeCheckingOptions {
    * will be included in the context type for the template. If `false`, any generic parameters will
    * be set to `any` in the template context type.
    *
-   * Defaults to `false`, even if "fullTemplateTypeCheck" is set.
+   * Defaults to `false`.
    */
   strictContextGenerics?: boolean;
 
   /**
    * Whether object or array literals defined in templates use their inferred type, or are
    * interpreted as `any`.
    *
-   * Defaults to `false` unless `fullTemplateTypeCheck` or `strictTemplates` are set.
+   * Defaults to `false` unless `strictTemplates` is set.
    */
   strictLiteralTypes?: boolean;
 }