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
This commit is contained in:
parent
2d5bb26b02
commit
76b77ec3c2
|
@ -57,8 +57,8 @@ const resolvedPromise = (() => Promise.resolve(null))();
|
||||||
*
|
*
|
||||||
* ### Migrating from deprecated ngForm selector
|
* ### Migrating from deprecated ngForm selector
|
||||||
*
|
*
|
||||||
* Support for using `ngForm` element selector has been deprecated in Angular v6 and will be removed
|
* Support for using `ngForm` element selector has been deprecated in Angular v6 and may be removed
|
||||||
* in Angular v9.
|
* in Angular v9 or later.
|
||||||
*
|
*
|
||||||
* This has been deprecated to keep selectors consistent with other core Angular selectors,
|
* This has been deprecated to keep selectors consistent with other core Angular selectors,
|
||||||
* as element selectors are typically written in kebab-case.
|
* as element selectors are typically written in kebab-case.
|
||||||
|
|
Loading…
Reference in New Issue