From 76b77ec3c2f1649be12ae892f8edf5c74c1ea707 Mon Sep 17 00:00:00 2001 From: Igor Minar Date: Sat, 8 Feb 2020 21:33:39 -0800 Subject: [PATCH] docs(forms): update the ngForm deprecation notice (#35263) we should be documenting when an API is eligible for removal and not when it will be removed. The actual removal depends on many factors, e.g. if we were able to automate the refactoring to the recommended API in time or not. PR Close #35263 --- packages/forms/src/directives/ng_form.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/forms/src/directives/ng_form.ts b/packages/forms/src/directives/ng_form.ts index f692468c0c..674664f645 100644 --- a/packages/forms/src/directives/ng_form.ts +++ b/packages/forms/src/directives/ng_form.ts @@ -57,8 +57,8 @@ const resolvedPromise = (() => Promise.resolve(null))(); * * ### Migrating from deprecated ngForm selector * - * Support for using `ngForm` element selector has been deprecated in Angular v6 and will be removed - * in Angular v9. + * Support for using `ngForm` element selector has been deprecated in Angular v6 and may be removed + * in Angular v9 or later. * * This has been deprecated to keep selectors consistent with other core Angular selectors, * as element selectors are typically written in kebab-case.