This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-21
Channels
- # aleph (2)
- # announcements (2)
- # babashka (10)
- # beginners (117)
- # calva (11)
- # cider (19)
- # clj-kondo (27)
- # cljs-dev (24)
- # cljsjs (1)
- # clojure (73)
- # clojure-europe (3)
- # clojure-italy (2)
- # clojure-nl (47)
- # clojure-spec (23)
- # clojure-uk (28)
- # clojurescript (71)
- # cursive (7)
- # data-science (17)
- # datascript (1)
- # datomic (7)
- # duct (23)
- # emacs (23)
- # fulcro (6)
- # graalvm (41)
- # jobs (2)
- # luminus (1)
- # malli (1)
- # off-topic (151)
- # pathom (1)
- # portkey (10)
- # re-frame (12)
- # reitit (17)
- # shadow-cljs (158)
- # spacemacs (14)
- # sql (8)
- # tools-deps (17)
- # xtdb (9)
@pwojnowski I think the best way to do this is with service workers. Though forcing an update on the user would be a bad experience. I’ve seen people design a notification that lets them know there is a new version of the app and triggers a refresh/fetches the new version
hi 0.11.0-rc3 (2019-11-20)
this is the third release candidate is there a planned date when it will be released
Correct, there are still some reagent 0.9.0-rc3 issues being resolved in reagent itself.
I'm trying to get a devcards/re-frame/testing-library setup going and running into some trouble with the timing of state changes
specifically, my tests that verify certain elements are visible after a dispatch aren't necessarily getting the latest state
I understand this is by design
a dispatch will eventually be reflected on the ui
for tests though, is there some recommendations on how one could sync things? like forcing ticks