docs(ngRepeat): mention limitations of object iteration #13978
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
Narretz
force-pushed
the
docs-ngrepeat-objects
branch
from
7752618 to
08fed81
Compare
|
CLAs look good, thanks! |
1 similar comment
|
CLAs look good, thanks! |
| * objects, and will throw if used with one. | ||
| * | ||
| * If you are hitting any of these limitations, the recommended workaround is to convert your object into an array | ||
| * that is sorted into the order that you prefer before providing it to `ngRepeat`. You could | ||
| * do this with a filter such as [toArrayFilter](http://ngmodules.org/modules/angular-toArrayFilter) | ||
| * or implement a `$watch` on the object yourself. |
There was a problem hiding this comment.
I wonder what it means to "implement a $watch on the object yourself". Any idea ?
There was a problem hiding this comment.
Maybe a watch that detects an object and then transforms it into an array?
|
LGTM |
Narretz
force-pushed
the
docs-ngrepeat-objects
branch
from
08fed81 to
8872e1e
Compare
Issue is tracked in issue Related #6266