This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-20
Channels
- # aleph (2)
- # boot (18)
- # cider (3)
- # cljs-dev (14)
- # cljsrn (28)
- # clojure (428)
- # clojure-austin (3)
- # clojure-hk (1)
- # clojure-ireland (5)
- # clojure-mexico (1)
- # clojure-quebec (2)
- # clojure-russia (49)
- # clojure-spec (138)
- # clojure-uk (45)
- # clojurescript (70)
- # core-async (1)
- # cursive (8)
- # datomic (13)
- # defnpodcast (3)
- # devops (1)
- # editors (4)
- # events (1)
- # funcool (14)
- # hoplon (17)
- # jobs-rus (1)
- # luminus (5)
- # mount (51)
- # off-topic (21)
- # om (9)
- # om-next (8)
- # onyx (43)
- # planck (6)
- # re-frame (13)
- # reagent (18)
- # ring-swagger (1)
- # spacemacs (17)
- # untangled (18)
- # vim (13)
- # yada (21)
I was able to solve the problem I described earlier by implementing componentDidUpdate fwiw
I’ve been trying to cope with om.next idents today. I find it very weird that ui components are in charge of determining the identities of application entities, but whatever, I can roll with it I guess. I think I even understand how the remote send-fn should report the replacement of temporary ids to the reconciler.
What I don’t have any answer for yet is how an om.next system should handle entities that want to change their identities. For example, an entity might want to save its state under a new identity (save as…)
@donaldball: Do you have a concrete example for what you’re asking?
I don’t think what you’re asking would be too problematic
has anyone used ReactCSSTransitionGroup
in om.next app https://facebook.github.io/react/docs/animation.html?