From 34d2988d14a9e4533c2f95a7b478c23ad1ed7d48 Mon Sep 17 00:00:00 2001 From: "Lincoln Baxter, III" Date: Fri, 8 Jan 2021 10:45:48 -0500 Subject: [PATCH] docs: Fix compiler option name reference (#40362) The `skipTemplateCodegen` option was incorrectly referenced using camelcase `skipTemplateCodeGen`. PR Close #40362 --- aio/content/guide/angular-compiler-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/angular-compiler-options.md b/aio/content/guide/angular-compiler-options.md index 9f4e4a7fd9..26d6b78671 100644 --- a/aio/content/guide/angular-compiler-options.md +++ b/aio/content/guide/angular-compiler-options.md @@ -180,7 +180,7 @@ For library projects generated with the CLI, the dev configuration default is `t ### `strictMetadataEmit` When `true`, reports an error to the `.metadata.json` file if `"skipMetadataEmit"` is `false`. -Default is `false`. Use only when `"skipMetadataEmit"` is `false` and `"skipTemplateCodeGen"` is `true`. +Default is `false`. Use only when `"skipMetadataEmit"` is `false` and `"skipTemplateCodegen"` is `true`. This option is intended to validate the `.metadata.json` files emitted for bundling with an `npm` package. The validation is strict and can emit errors for metadata that would never produce an error when used by the template compiler. You can choose to suppress the error emitted by this option for an exported symbol by including `@dynamic` in the comment documenting the symbol.