cargdev/angular
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clean up deprecation guide (#33338)

Browse Source 
PR Close #33338
This commit is contained in:
Kara Erickson
2019-10-22 17:49:25 -07:00
committed by Andrew Kushnir
parent 49eec5d872
commit 383457f898
3 changed files with 58 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
packages/forms/src/directives/reactive_directives/form_control_directive.ts
View File

@ -47,7 +47,8 @@ export const formControlBinding: any = {
* ### Use with ngModel
*
* Support for using the `ngModel` input property and `ngModelChange` event with reactive
* form directives has been deprecated in Angular v6 and will be removed in Angular v7.
* form directives has been deprecated in Angular v6 and will be removed in a future version
* of Angular.
*
* Now deprecated:
*
@ -73,9 +74,9 @@ export const formControlBinding: any = {
* principles behind reactive forms, whereas adding a `FormControl`/`FormGroup` layer in
* the class removes the convenience of defining forms in the template.
*
* To update your code before v7, you'll want to decide whether to stick with reactive form
* directives (and get/set values using reactive forms patterns) or switch over to
* template-driven directives.
* To update your code before support is removed, you'll want to decide whether to stick
* with reactive form directives (and get/set values using reactive forms patterns) or
* switch over to template-driven directives.
*
* After (choice 1 - use reactive forms):
*

7
packages/forms/src/directives/reactive_directives/form_control_name.ts
View File

@ -53,7 +53,8 @@ export const controlNameBinding: any = {
* ### Use with ngModel
*
* Support for using the `ngModel` input property and `ngModelChange` event with reactive
* form directives has been deprecated in Angular v6 and will be removed in Angular v7.
* form directives has been deprecated in Angular v6 and will be removed in a future
* version of Angular.
*
* Now deprecated:
*
@ -81,8 +82,8 @@ export const controlNameBinding: any = {
* principles behind reactive forms, whereas adding a `FormControl`/`FormGroup` layer in
* the class removes the convenience of defining forms in the template.
*
* To update your code before v7, you'll want to decide whether to stick with reactive form
* directives (and get/set values using reactive forms patterns) or switch over to
* To update your code before support is removed, you'll want to decide whether to stick with
* reactive form directives (and get/set values using reactive forms patterns) or switch over to
* template-driven directives.
*
* After (choice 1 - use reactive forms):