diff options
| author | Peter Bacon Darwin | 2014-02-14 14:12:13 +0000 | 
|---|---|---|
| committer | Peter Bacon Darwin | 2014-02-16 19:03:43 +0000 | 
| commit | d85505d0194e6aa2cfe24aea51afe12a09ba73d2 (patch) | |
| tree | d9357a6298962948f77af4187a43616f284ff4df /docs/content/guide/forms.ngdoc | |
| parent | daa83f2864cbcdce9fa650bba363334824ff5859 (diff) | |
| download | angular.js-d85505d0194e6aa2cfe24aea51afe12a09ba73d2.tar.bz2 | |
docs(content): fix bad links
Diffstat (limited to 'docs/content/guide/forms.ngdoc')
| -rw-r--r-- | docs/content/guide/forms.ngdoc | 16 | 
1 files changed, 8 insertions, 8 deletions
| diff --git a/docs/content/guide/forms.ngdoc b/docs/content/guide/forms.ngdoc index d5f59d18..2ef5e218 100644 --- a/docs/content/guide/forms.ngdoc +++ b/docs/content/guide/forms.ngdoc @@ -14,7 +14,7 @@ Server-side validation is still necessary for a secure application.  # Simple form  The key directive in understanding two-way data-binding is {@link ng.directive:ngModel ngModel}.  The `ngModel` directive provides the two-way data-binding by synchronizing the model to the view, as well as view to the model. -In addition it provides an {@link ng.directive:ngModel.NgModelController API} for other directives to augment its behavior. +In addition it provides an {@link ngModel.NgModelController API} for other directives to augment its behavior.  <doc:example>  <doc:source> @@ -113,11 +113,11 @@ This ensures that the user is not distracted with an error until after interacti  # Binding to form and control state -A form is an instance of {@link ng.directive:form.FormController FormController}. +A form is an instance of {@link form.FormController FormController}.  The form instance can optionally be published into the scope using the `name` attribute.  Similarly, an input control that has the {@link ng.directive:ngModel ngModel} directive holds an -instance of {@link ng.directive:ngModel.NgModelController NgModelController}. +instance of {@link ngModel.NgModelController NgModelController}.  Such a control instance can be published as a property of the form instance using the `name` attribute  on the input control.  The name attribute specifies the name of the property on the form instance. @@ -184,18 +184,18 @@ This allows us to extend the above example with these features:  # Custom Validation  Angular provides basic implementation for most common html5 {@link ng.directive:input input} -types: ({@link ng.directive:input.text text}, {@link ng.directive:input.number number}, {@link ng.directive:input.url url}, {@link ng.directive:input.email email}, {@link ng.directive:input.radio radio}, {@link ng.directive:input.checkbox checkbox}), as well as some directives for validation (`required`, `pattern`, `minlength`, `maxlength`, `min`, `max`). +types: ({@link input[text] text}, {@link input[number] number}, {@link input[url] url}, {@link input[email] email}, {@link input[radio] radio}, {@link input[checkbox] checkbox}), as well as some directives for validation (`required`, `pattern`, `minlength`, `maxlength`, `min`, `max`). -Defining your own validator can be done by defining your own directive which adds a custom validation function to the `ngModel` {@link ng.directive:ngModel.NgModelController controller}. +Defining your own validator can be done by defining your own directive which adds a custom validation function to the `ngModel` {@link ngModel.NgModelController controller}.  To get a hold of the controller the directive specifies a dependency as shown in the example below.  The validation can occur in two places:    * **Model to View update** - -    Whenever the bound model changes, all functions in {@link ng.directive:ngModel.NgModelController#properties_$formatters NgModelController#$formatters} array are pipe-lined, so that each of these functions has an opportunity to format the value and change validity state of the form control through {@link ng.directive:ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}. +    Whenever the bound model changes, all functions in {@link ngModel.NgModelController#properties_$formatters NgModelController#$formatters} array are pipe-lined, so that each of these functions has an opportunity to format the value and change validity state of the form control through {@link ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}.    * **View to Model update** - -    In a similar way, whenever a user interacts with a control it calls {@link ng.directive:ngModel.NgModelController#methods_$setViewValue NgModelController#$setViewValue}. -This in turn pipelines all functions in the {@link ng.directive:ngModel.NgModelController#properties_$parsers NgModelController#$parsers} array, so that each of these functions has an opportunity to convert the value and change validity state of the form control through {@link ng.directive:ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}. +    In a similar way, whenever a user interacts with a control it calls {@link ngModel.NgModelController#methods_$setViewValue NgModelController#$setViewValue}. +This in turn pipelines all functions in the {@link ngModel.NgModelController#properties_$parsers NgModelController#$parsers} array, so that each of these functions has an opportunity to convert the value and change validity state of the form control through {@link ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}.  In the following example we create two directives. | 
