Fork me on GitHub
#om
<
2017-07-31
>
wilkerlucio13:07:23

@ghopper but as a recommendation, try to avoid nesting, I figure that if you keep your local database flat you will have an easier time managing it

timovanderkamp14:07:00

Using the (om/children) function will basically always result into the react keys warning, saying that you must provide an unique key property for every element in the list. I thought a simple (apply dom/div (om/children this)) would prevent the warning from happening but it doesnt seem to work. Is the only solution to provide a unique key prop for each element?

roklenarcic15:07:08

I think it only needs to be unique for a specific list

roklenarcic15:07:49

so using numeric IDs from 0...n for each element in the list is OK

rarous18:07:25

@roklenarcic not always true. keys has to be unique if items can be reordered between rerenders.

roklenarcic18:07:41

I don't get a warning if I reuse keys in two separate lists