Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit 36a14e6

Browse files
docs(select): link to ngOptions
Closes #10854
1 parent 3228d3b commit 36a14e6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/ng/directive/select.js

+4-4
Original file line numberDiff line numberDiff line change
@@ -114,12 +114,12 @@ var SelectController =
114114
* @description
115115
* HTML `SELECT` element with angular data-binding.
116116
*
117-
* In many cases, `ngRepeat` can be used on `<option>` elements instead of `ngOptions` to achieve a
118-
* similar result. However, `ngOptions` provides some benefits such as reducing memory and
119-
* increasing speed by not creating a new scope for each repeated instance, as well as providing
117+
* In many cases, `ngRepeat` can be used on `<option>` elements instead of {@link ng.directive:ngOptions
118+
* ngOptions} to achieve a similar result. However, `ngOptions` provides some benefits such as reducing
119+
* memory and increasing speed by not creating a new scope for each repeated instance, as well as providing
120120
* more flexibility in how the `<select>`'s model is assigned via the `select` **`as`** part of the
121121
* comprehension expression. `ngOptions` should be used when the `<select>` model needs to be bound
122-
* to a non-string value. This is because an option element can only be bound to string values at
122+
* to a non-string value. This is because an option element can only be bound to string values at
123123
* present.
124124
*
125125
* When an item in the `<select>` menu is selected, the array element or object property

0 commit comments

Comments
 (0)