This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-31
Channels
- # beginners (9)
- # boot (38)
- # cider (7)
- # cljs-dev (181)
- # cljsrn (49)
- # clojure (136)
- # clojure-italy (44)
- # clojure-losangeles (1)
- # clojure-news (1)
- # clojure-russia (3)
- # clojure-sanfrancisco (1)
- # clojure-serbia (2)
- # clojure-spec (28)
- # clojure-uk (41)
- # clojure-ukraine (1)
- # clojurescript (103)
- # core-async (6)
- # core-logic (46)
- # cursive (5)
- # data-science (8)
- # datascript (6)
- # datomic (5)
- # emacs (35)
- # events (3)
- # jobs (2)
- # jobs-rus (2)
- # juxt (6)
- # lumo (7)
- # off-topic (101)
- # om (6)
- # onyx (6)
- # parinfer (38)
- # pedestal (5)
- # perun (1)
- # planck (4)
- # protorepl (4)
- # re-frame (62)
- # reagent (20)
- # remote-jobs (1)
- # ring-swagger (1)
- # spacemacs (16)
- # unrepl (43)
- # vim (13)
@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
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?
I think it only needs to be unique for a specific list
so using numeric IDs from 0...n for each element in the list is OK
@roklenarcic not always true. key
s has to be unique if items can be reordered between rerenders.
I don't get a warning if I reuse keys in two separate lists