This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-19
Channels
- # admin-announcements (2)
- # aws-lambda (3)
- # beginners (66)
- # boot (61)
- # cider (1)
- # cljs-dev (17)
- # clojure (100)
- # clojure-austin (4)
- # clojure-brasil (1)
- # clojure-canada (8)
- # clojure-quebec (6)
- # clojure-russia (48)
- # clojure-sg (6)
- # clojure-spec (37)
- # clojure-uk (61)
- # clojure-ukraine (2)
- # clojurescript (80)
- # core-async (13)
- # cursive (20)
- # datascript (37)
- # datomic (2)
- # defnpodcast (4)
- # emacs (5)
- # funcool (3)
- # hoplon (11)
- # jobs (7)
- # juxt (26)
- # lein-figwheel (48)
- # leiningen (3)
- # luminus (3)
- # om (34)
- # om-next (5)
- # onyx (5)
- # protorepl (6)
- # re-frame (10)
- # reagent (9)
- # rethinkdb (16)
- # ring-swagger (5)
- # spacemacs (14)
- # specter (54)
- # untangled (36)
- # vim (75)
- # yada (1)
hi, I am trying om-next to create a new project, and I used to use version alpha32, and today upgrade to alpha40
but it comes to the react warning message, flattenChildren(...): Encountered two children with the same key,
.$undefined`. Child keys must be unique; when two children share a key, only the first child will be used.`
it seems it comes from the upgrade of react from 0.14 to 15, but I checked the examples of om-next, it does not set the react key frequently...what's the trick here?
currently, I created the components following the examples, use defui and factory, but it always comes the react flattenchildren message, even I change the content of component to the simple text string
@joseph: you might want to try adding :keyfn to factory: https://github.com/omcljs/om/wiki/Documentation-%28om.next%29#factory