This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-19
Channels
- # bangalore-clj (35)
- # beginners (42)
- # boot (89)
- # cider (9)
- # clara (2)
- # cljs-dev (29)
- # cljsjs (3)
- # cljsrn (14)
- # clojars (9)
- # clojure (332)
- # clojure-brasil (1)
- # clojure-dev (5)
- # clojure-italy (4)
- # clojure-russia (36)
- # clojure-spec (38)
- # clojure-uk (65)
- # clojurescript (114)
- # clr (11)
- # community-development (105)
- # core-async (10)
- # cursive (4)
- # datascript (1)
- # datomic (58)
- # defnpodcast (3)
- # emacs (4)
- # hoplon (7)
- # juxt (3)
- # keechma (8)
- # off-topic (7)
- # om (109)
- # om-next (8)
- # onyx (26)
- # pedestal (3)
- # planck (8)
- # re-frame (76)
- # reagent (28)
- # rum (25)
- # spacemacs (2)
- # specter (35)
- # untangled (31)
- # yada (27)
i'm seeing some exceptions that make me think that where I need to ensure there's default values for props
ok thanks, the render with nil in props are happening through some other way then, that helps narrow it down thanks
@jasonjckn I feel like I've encountered something similar (initial render had nil
props, everywhere)
I think in my case it was due to misshapen data being returned from my initial server api-read
.
thanks for the input, i'm following a thread right now on it my Root query has {:foo (get-query FooComponent)} which means :foo is read from global state , but also I have an ident [:foo X]
Started looking at Compassus a bit. Is there a way to use Compassus and Untangled together? Looks like they both want to wrap the application
btw, the other day you were right about the loading data bit after I added a leaf component. The shape of the incoming data needed to change.
I dunno if this is useful @grzm, since looks like Compassus is pretty full-featured, but for us it was sufficient to just use Pushy with a bit of custom wrapping which basically boiled down to make it so on each route change event we call om/transact!
to update :ui/current-route in the app state.
@therabidbanana Yeah, I was thinking the same when I was looking over the Compassus README. @anmonteiro your README is really good 馃檪
One thing we found useful with that approach is "post-transactions" that the routing event tacks on for certain pages to get data to load, etc.
@grzm I don鈥檛 know when you looked at Compassus
so you already saw the mixin stuff
I鈥檓 planning on moving e.g. the :history
config key to be a mixin too
since it鈥檚 just something that hooks into the root component lifecycle
so some changes coming to the next release
just a heads up
but migration will be very straightforward
Cool. At this point I'm just looking at it for ideas that I can integrate into my existing Untangled app. And there are a lot of good ideas in there.
e.g. this was the only thing that we needed to migrate from :wrapper
to a mixin:
https://github.com/compassus/compassus/commit/b63876a806bb03b3e462754136bfcd24fdf2001b#diff-a6beef26a2a83ef9397df32b89e26117L114
Ever since Cellophane existed, yea 馃槢