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

docs(forms): remove unnecessary {@link Injector} jsdoc tags (#23186)

Browse Source 
Inline code blocks are automatically linked, if possible, to their API
page.

PR Close #23186
This commit is contained in:
Pete Bacon Darwin
2018-04-05 10:58:12 +01:00
committed by Igor Minar
parent 1aef4df127
commit 92821e338b
23 changed files with 136 additions and 136 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
packages/forms/src/directives/ng_model.ts
View File

@ -48,10 +48,10 @@ const resolvedPromise = Promise.resolve(null);
/**
* @description
*
* Creates a {@link FormControl} instance from a domain model and binds it
* Creates a `FormControl` instance from a domain model and binds it
* to a form control element.
*
* The {@link FormControl} instance will track the value, user interaction, and
* The `FormControl` instance will track the value, user interaction, and
* validation status of the control and keep the view synced with the model. If used
* within a parent form, the directive will also register itself with the form as a child
* control.
@ -59,18 +59,18 @@ const resolvedPromise = Promise.resolve(null);
* This directive can be used by itself or as part of a larger form. All you need is the
* `ngModel` selector to activate it.
*
* It accepts a domain model as an optional {@link Input}. If you have a one-way binding
* It accepts a domain model as an optional `Input`. If you have a one-way binding
* to `ngModel` with `[]` syntax, changing the value of the domain model in the component
* class will set the value in the view. If you have a two-way binding with `[()]` syntax
* (also known as 'banana-box syntax'), the value in the UI will always be synced back to
* the domain model in your class as well.
*
* If you wish to inspect the properties of the associated {@link FormControl} (like
* If you wish to inspect the properties of the associated `FormControl` (like
* validity state), you can also export the directive into a local template variable using
* `ngModel` as the key (ex: `#myVar="ngModel"`). You can then access the control using the
* directive's `control` property, but most properties you'll need (like `valid` and `dirty`)
* will fall through to the control anyway, so you can access them directly. You can see a
* full list of properties directly available in {@link AbstractControlDirective}.
* full list of properties directly available in `AbstractControlDirective`.
*
* The following is an example of a simple standalone control using `ngModel`:
*
@ -94,8 +94,8 @@ const resolvedPromise = Promise.resolve(null);
*
* To see `ngModel` examples with different form control types, see:
*
* * Radio buttons: {@link RadioControlValueAccessor}
* * Selects: {@link SelectControlValueAccessor}
* * Radio buttons: `RadioControlValueAccessor`
* * Selects: `SelectControlValueAccessor`
*
* **npm package**: `@angular/forms`
*