This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-19
Channels
- # announcements (1)
- # beginners (115)
- # calva (7)
- # cider (8)
- # clj-kondo (3)
- # cljdoc (12)
- # clojure (50)
- # clojure-europe (4)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-spec (70)
- # clojure-uk (88)
- # clojurescript (54)
- # core-async (16)
- # cursive (5)
- # datomic (31)
- # editors (4)
- # emacs (4)
- # fulcro (29)
- # graphql (17)
- # luminus (1)
- # lumo (2)
- # off-topic (37)
- # pathom (16)
- # random (2)
- # re-frame (5)
- # reitit (3)
- # rum (2)
- # shadow-cljs (192)
- # sql (11)
contribute a port @grant ??? The old source won’t take much to adapt…just have not had time, and don’t use myself.
glad to point out the parts to do…There should be adequate hooks for it to all work well
We are porting to Fulcro 3 and we used to have our own version of the dynamic routers (because we ran into timing issues from time to time). But we also seem to have issues with Fulcro3 dynamic routing... Fulcro inspect makes me think there is some kind of timing issue:
Could you look at the state machine in app state at each of those interactions? The ::uism/asm-id table holds router state machines by their fqname (as shown in tx log). Be interested in what current-state is.
The timer for failure starts on deferred, and is supposed to be cancelled on target ready.
I stuck a try/catch in uism near the timer cancels..perhaps a handler threw an exception. Try Beta 18 SNAPSHOT
On thing that we noticed it that it only seems to happen when we a render body to the defrouter, so maybe that triggers some extra case
This is with RC1 btw
@mitchelkuijpers what’s the situation? i.e. what do you expect to happen that’s not happing?
It goes to loading an then to failed, while the load succeeds
It happens randomly
It should stop at :ready
Hm. I thought we had gotten all of the timing issues fixed. The easy workaround is to use route-immediate, and use load markers in state instead. If you feel like trying to make a repro case I’d be glad to look at it.
I'll use route-immediate for now, I need to get this project out. And then make a reproduction.
This is at a user event
The state machine might need another “edge” for ready events…perhaps it was in the wrong state when you called route ready.
No I don't get any warning or error