From 71be1da0ada983a6bca6eec9bc031fcd1aa7680d Mon Sep 17 00:00:00 2001 From: Trotyl Yu Date: Thu, 30 May 2019 01:39:30 +0800 Subject: [PATCH] docs: fix deprecation information (#30717) PR Close #30717 --- aio/content/guide/deprecations.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/aio/content/guide/deprecations.md b/aio/content/guide/deprecations.md index aea0be6915..82af74b934 100644 --- a/aio/content/guide/deprecations.md +++ b/aio/content/guide/deprecations.md @@ -318,8 +318,6 @@ The need for this polyfill was removed in Angular version 8.0 ([see #14473](http In a typical Angular project, the polyfill is not used in production builds, so removing it should not impact production applications. The goal behind this removal is overall simplification of the build setup and decrease in the number of external dependencies. -We expect to remove the polyfill from most if not all CLI projects via an `ng upgrade` migration from version 8 to 9. - {@a static-query-resolution} ### `@ViewChild()` / `@ContentChild()` static resolution as the default