From 09cc458bfc0ed90a055b3aaccd07aff9257b6de9 Mon Sep 17 00:00:00 2001 From: lovelangy Date: Thu, 11 Oct 2018 15:31:17 +1000 Subject: [PATCH] docs: type fix (#26386) according to the source code and the doc https://angular.io/api/forms/NgModel#inherited-from-formsngcontrol-1, the method name should be "viewToModelUpdate" instead of "viewToModel" PR Close #26386 --- aio/content/guide/forms-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/forms-overview.md b/aio/content/guide/forms-overview.md index c8d2b112e0..07ad5f1159 100644 --- a/aio/content/guide/forms-overview.md +++ b/aio/content/guide/forms-overview.md @@ -128,7 +128,7 @@ The steps below outline the view to model data flow. 1. The control value accessor attached to the input triggers the `setValue()` method on the `FormControl` instance. 1. The `FormControl` instance emits the new value through the `valueChanges` observable. 1. Any subscribers to the `valueChanges` observable receive the new value. -1. The control value accessor also calls the `NgModel.viewToModel()` method which emits an `ngModelChange` event. +1. The control value accessor also calls the `NgModel.viewToModelUpdate()` method which emits an `ngModelChange` event. 1. Because the component template uses two-way data binding for the `favoriteColor`, the `favoriteColor` property in the component is updated to the value emitted by the `ngModelChange` event ("Blue").