Tracking down unique key prop violations about reagent

[holmsand]

Yep, been there as well…

It would be very useful if React included the entire path of the component in its error messages, and not just the name.

What I have done when trying to find the offending component is to change the name of some of the suspects. Reagent sets displayName to the entire name of the tag (for built-in components), so if you use e.g :li.suspect1, :li.suspect2, etc these full names should show up in the error messages (and, as you say, in the Chrome developer tools).

Note also that you only need to look for seqs. They are converted into javascript arrays (hence React's error message), and their top-level components are the ones that should have a key.

[ptaoussanis]

It would be very useful if React included the entire path of the component in its error messages, and not just the name.

That would be very helpful. Will see about suggesting it on the group.

Note also that you only need to look for seqs. They are converted into javascript arrays (hence React's error message), and their top-level components are the ones that should have a key.

What I have done when trying to find the offending component is to change the name of some of the suspects.

Ahh, hadn't realised that would show in the displayName, thanks!