This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-31
Channels
- # announcements (1)
- # aws (4)
- # babashka (40)
- # beginners (89)
- # calva (13)
- # cider (3)
- # clj-kondo (36)
- # cljdoc (16)
- # clojure (74)
- # clojure-boston (1)
- # clojure-dev (7)
- # clojure-europe (30)
- # clojure-new-zealand (1)
- # clojure-nl (17)
- # clojure-uk (5)
- # clojurescript (16)
- # core-async (9)
- # cursive (16)
- # datahike (3)
- # datalog (6)
- # datascript (7)
- # datomic (15)
- # emacs (38)
- # events (2)
- # figwheel-main (3)
- # fulcro (6)
- # google-cloud (18)
- # graalvm (6)
- # gratitude (1)
- # honeysql (1)
- # introduce-yourself (1)
- # jobs (1)
- # leiningen (5)
- # lsp (6)
- # malli (11)
- # meander (2)
- # off-topic (4)
- # re-frame (6)
- # reitit (8)
- # releases (2)
- # remote-jobs (3)
- # reveal (4)
- # shadow-cljs (200)
- # sql (8)
- # tools-deps (16)
Hrmh. I'm doing set-root! (with initialize), change-route, and mount! (with :initialize-state? false) and I'm still getting the ASM path warning. Tried explicit dr/initialize! too before changing the route, but that didn't help.
Ok, https://fulcro-community.github.io/guides/tutorial-advanced-minimalist-fulcro/#_the_bare_essentials_of_fulcro_routing mentions that it cannot be really avoided
I think I got rid of that error by not mounting the component with the root router… i.e. Root (mounted by React) -> Chrome (with router)
I've found rendering on the next turn of the event loop to work (the router is a state machine which uses transactions to work, which are async so this is a hack to let the transactions finish) https://github.com/dvingo/dv.fulcro-template/blob/5d69fefd7157f52bf725c362e794b9eacf3ea25d/resources/clj/new/dv.fulcro_template/src/main/app/client/client_entry.cljs#L46