Closed alberto-portilla closed 8 years ago
This most likely isn't this library's problem, more likely it's Om.Next. As a temporary workaround u can still just wrap it in divs and everything's okay.
(dom/div
nil
(dom/div nil (my-stepper))
(dom/div nil (my-stepper)))
True that, checked again and is an issue of om next, thanks on the heads-up
Based on the example provided, i tried to use two components on the same parent as seen in the code:
Doing this throws an error as the components are created with "undefined" react-key, causing the two elements to have the same key. Same happens when defining another component and using it.