This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-03
Channels
- # admin-announcements (6)
- # beginners (73)
- # boot (84)
- # cider (9)
- # cljs-edn (5)
- # cljs-site (8)
- # cljsrn (2)
- # clojure (158)
- # clojure-austin (1)
- # clojure-canada (1)
- # clojure-dusseldorf (2)
- # clojure-ireland (1)
- # clojure-russia (45)
- # clojure-sg (2)
- # clojure-uk (28)
- # clojurebridge (2)
- # clojurescript (142)
- # core-async (43)
- # cursive (23)
- # datascript (5)
- # datomic (9)
- # dirac (4)
- # emacs (23)
- # funcool (1)
- # garden (1)
- # hoplon (280)
- # jobs (1)
- # ldnclj (6)
- # leiningen (37)
- # luminus (6)
- # om (30)
- # om-next (1)
- # onyx (6)
- # perun (24)
- # re-frame (10)
- # reagent (20)
- # remote-jobs (1)
- # rethinkdb (2)
- # ring-swagger (4)
- # rum (3)
- # spacemacs (6)
- # untangled (36)
- # yada (5)
At app start I'm manually invoking secretary/dispatch! on the current token in history
That triggers a re-frame handler that updates the name of the current page to render
but it seems that it misses a few cycles, because it always starts rendering the default page for a few ms then jumps to the correct page
Is there a canonical way to make sure that all of the routing logic is setup and triggered correctly before starting rendering that I'm missing?
@aboekhoff: out of curiosity are you using the luminus template?
@nfisher: I started with the re-frame frontend only template. I think that might be my problem. I probably need to init the db, init the routes, and only then hook the navigation. I'll give that a try tonight. Thanks!
@aboekhoff: Do you use accountant.core/dispatch-current!
somewhere? In my understanding that's what triggers route on startup.