@tony.kay: First off, thanks for taking the time for all this - superb work! At the moment, yes. om
version in the client-only
branch may need to be bumped. But in my case the fruitless investigation before asking here taught me quite a bit. Becomes a bit of a trade off between the reassurance of having similar stuff on the screen and having to redo the videos every week because of tool and app changes. (eg. Using IntelliJ 2016.2)
@parameme: you mean client-only of todomvc?
I've pushed updates for todomvc to more recent versions
@tony.kay: I think the tabunion alternates are initialized after on-app-started has finished, this has lead to some confusion on my part where I try to initialize some app state in on-app-started, but it gets overwritten by tab union alternates InitialAppState
so I think the order should be (1) InitialAppState of Root (2) alternates (3) on-app-started
Um...I think I fixed that recently
what version?
not sure I did a release
I tested on the latest release 1.5 weeks ago I think
commit 054f3cc24935c3cbff619e3a7697e9fe30252055
might be on 0.5.5-SNAPSHOT only
yeah...that's it
If I have a few ppl that can tell me 0.5.5 seems stable (on reasonable apps) then I'll be glad to cut a release
is this pushed to github?
i'm looking for that commit
0.5.5-SNAPSHOT is
I can re-push to be sure
found it
k
great to see this fixed!
that was fast, i thought I would have to wait a while
😉
yeah, had someone else run into the same thing
is this the new order (1) InitialAppState of Root (2) alternates (3) on-app-started ?
don't remember 🙂 Let me look
Yes
k
line 103 of core.cljs does the initial state computation/set
114 does the alternates
line 116 calls started callback