-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(common): rewrite docs for NgForOf#ngForTrackBy #42329
Conversation
1b031b0
to
f2716b0
Compare
Clarify the prupose of the tracking function and document how to create a good one. Fixes angular#40461
@TeriGlover can you please take a look at this one as well? thank you! |
You can preview f2716b0 at https://pr42329-f2716b0.ngbuilds.io/. |
f2716b0
to
62ab9d6
Compare
62ab9d6
to
4197b82
Compare
You can preview 4197b82 at https://pr42329-4197b82.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @IgorMinar, do you think you could take on #35896 (in another PR) as well since it's related? The issue there is that the insertion order of VE just happened to work with ngFor
in the select (#35896 (comment)). All the items in the select array are new objects because of the map
function so Angular needs to be able to identify which ones are pre-existing via trackBy
.
Also, based on that issue maybe it's worth adding a special note in your description to call out the importance of trackBy
with select
elements and their options.
I'll take a look @atscott. Thanks for the review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Editing review complete; left several comments.
Editing review completed:
#42329 (review).
Several comments; otherwise, LGTM.
…On Tue, May 25, 2021 at 2:26 PM Igor Minar ***@***.***> wrote:
I'll take a look @atscott <https://github.com/atscott>. Thanks for the
review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42329 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4DPGWW72XEUIEN5UGAGQDTPQI2HANCNFSM45QF6BVA>
.
--
*--Teri Glover--*
*Technical Editor*
|
Hi Igor,
What is this second one; where can I find it?
Thanks,
--Teri
…On Tue, May 25, 2021 at 1:59 PM Igor Minar ***@***.***> wrote:
@TeriGlover <https://github.com/TeriGlover> can you please take a look at
this one as well? thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42329 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4DPGQ5RZCPZ2MP63DSO23TPQFTJANCNFSM45QF6BVA>
.
--
*--Teri Glover--*
*Technical Editor*
|
thanks for the review @TeriGlover, I'll work on the additions that Andrew brought up in a new PR and will ask you for a review. |
You can preview 4471331 at https://pr42329-4471331.ngbuilds.io/. |
Hi guys, This is much better now. Docs were missing the reorder part. Now it'a much more clearer. Many thanks! |
Clarify the prupose of the tracking function and document how to create a good one. Fixes angular#40461 PR Close angular#42329
Clarify the prupose of the tracking function and document how to create a good one. Fixes angular#40461 PR Close angular#42329
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Clarify the prupose of the tracking function and document how to create a good one.
Fixes #40461