This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-22
Channels
- # announcements (5)
- # aws (38)
- # aws-lambda (21)
- # babashka (45)
- # beginners (87)
- # boot (1)
- # calva (32)
- # cider (23)
- # clara (7)
- # clj-kondo (41)
- # cljs-dev (29)
- # clojure (145)
- # clojure-europe (6)
- # clojure-italy (12)
- # clojure-nl (4)
- # clojure-spec (39)
- # clojure-uk (45)
- # clojurescript (171)
- # copenhagen-clojurians (4)
- # cursive (14)
- # datomic (48)
- # docker (6)
- # figwheel-main (2)
- # fulcro (54)
- # jackdaw (1)
- # jobs (1)
- # kaocha (3)
- # leiningen (7)
- # luminus (6)
- # malli (2)
- # off-topic (51)
- # pathom (8)
- # quil (20)
- # re-frame (14)
- # reagent (1)
- # reitit (2)
- # remote-jobs (1)
- # shadow-cljs (39)
- # tools-deps (1)
- # vim (12)
- # xtdb (5)
I may have something setup wrong, but when using reitit/front-end
controllers to dispatch re-frame events I’m seeing a dramatic slow down in the ability of the UI to update in response to an app-db change.
In this case a nav-link
which renders with a different background color if it is the active page. When I add a re-frame dispatch of a graphql query to the start
controller, it takes much longer for the nav link to change color. Though it seems like the events are still happening in the order of navigate!
-> navigated
-> start-controller logic
when inspected with 10x
. It seems because of the logic in the controller, components that depend on app-db changes made by the navigated
event slow down.