diff options
| author | James deBoer | 2013-03-24 23:11:36 -0700 |
|---|---|---|
| committer | Igor Minar | 2013-04-04 09:29:51 -0700 |
| commit | cd6dd22b19cc19ab034e3e39518cc454bf53570d (patch) | |
| tree | 1dcd53423b961f8b43de1981365d9488654e8e10 | |
| parent | 139c5320191ec5e9f37ba689c5e8e917087f6bfb (diff) | |
| download | angular.js-cd6dd22b19cc19ab034e3e39518cc454bf53570d.tar.bz2 | |
Update forms.ngdoc
docs(forms): Fixed a typo. render -> $render
| -rw-r--r-- | docs/content/guide/forms.ngdoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/content/guide/forms.ngdoc b/docs/content/guide/forms.ngdoc index 9a02029a..3d093467 100644 --- a/docs/content/guide/forms.ngdoc +++ b/docs/content/guide/forms.ngdoc @@ -278,7 +278,7 @@ However, if you need more flexibility, you can write your own form control as a In order for custom control to work with `ngModel` and to achieve two-way data-binding it needs to: - - implement `render` method, which is responsible for rendering the data after it passed the {@link api/ng.directive:ngModel.NgModelController#$formatters NgModelController#$formatters}, + - implement `$render` method, which is responsible for rendering the data after it passed the {@link api/ng.directive:ngModel.NgModelController#$formatters NgModelController#$formatters}, - call `$setViewValue` method, whenever the user interacts with the control and model needs to be updated. This is usually done inside a DOM Event listener. See {@link guide/directive $compileProvider.directive} for more info. |