Skip to content

Warn better for key issues#1351

Closed
zpao wants to merge 1 commit intofacebook:masterfrom
zpao:key-warn-harder-better-faster-stronger
Closed

Warn better for key issues#1351
zpao wants to merge 1 commit intofacebook:masterfrom
zpao:key-warn-harder-better-faster-stronger

Conversation

@zpao
Copy link
Member

@zpao zpao commented Apr 3, 2014

We weren't warning for key issues at the top level (renderComponent) level at
all. This makes us do that, even if it's not quite perfect.

@sebmarkbage complained to me after it went in that #1334 wasn't really the right fix (true, but it was needed).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<3 quasis

@sophiebits
Copy link
Collaborator

accept

I was going to do this but didn't get around to it. Fixes #1333.

clowncopterize

@sebmarkbage
Copy link
Contributor

Be careful about perf here. This is one of the most expensive code paths in dev.

@sophiebits
Copy link
Collaborator

I think the only thing here that might be sketchy about perf is the creation of the displayNames object?

@zpao
Copy link
Member Author

zpao commented Apr 4, 2014

Yea, going to move that out since it's not used every time, but this fn is called for every child ever.

We weren't warning for key issues at the top level (renderComponent) level at
all. This makes us do that, even if it's not quite perfect.
@zpao zpao closed this in af3c04b Apr 8, 2014
@zpao zpao deleted the key-warn-harder-better-faster-stronger branch October 30, 2014 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants