Fork me on GitHub
#untangled
<
2016-09-19
>
grzm14:09:51

@tony.kay that's really cool 馃檪 Nice!

jasonjckn19:09:28

Is there a render that happens before the InitialAppState is merged in?

jasonjckn19:09:43

i'm seeing some exceptions that make me think that where I need to ensure there's default values for props

tony.kay19:09:43

IAS has to be given to reconciler, so no

jasonjckn19:09:12

ok thanks, the render with nil in props are happening through some other way then, that helps narrow it down thanks

ecaspary19:09:46

@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.

jasonjckn19:09:23

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]

jasonjckn19:09:26

so i think there's conflict

jasonjckn19:09:39

(FooComponent has ident [:foo X])

grzm19:09:43

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

grzm20:09:33

that's what I suspected 馃檪

grzm20:09:00

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.

therabidbanana20:09:41

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.

grzm20:09:34

@therabidbanana Yeah, I was thinking the same when I was looking over the Compassus README. @anmonteiro your README is really good 馃檪

therabidbanana20:09:37

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.

anmonteiro20:09:38

@grzm I don鈥檛 know when you looked at Compassus

grzm20:09:45

Yesterday

anmonteiro20:09:53

so you already saw the mixin stuff

grzm20:09:16

Yup. I have an allergy to mixins, so I'll admit I haven't looked at them too closely

anmonteiro20:09:29

I鈥檓 planning on moving e.g. the :history config key to be a mixin too

anmonteiro20:09:43

since it鈥檚 just something that hooks into the root component lifecycle

anmonteiro20:09:54

so some changes coming to the next release

anmonteiro20:09:57

just a heads up

anmonteiro20:09:06

but migration will be very straightforward

grzm20:09:36

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.

grzm20:09:36

Do you generally write most of your code cljc at this point?

anmonteiro20:09:07

Ever since Cellophane existed, yea 馃槢

grzm20:09:57

I think the number of cljc namespaces I've created at this point is still less than 5 馃檪

grzm20:09:23

Good habit to get into, though, if writing web apps with a server component. Also helps reinforce the distinctions between the two implementations.