This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-26
Channels
- # aleph (9)
- # announcements (31)
- # babashka (23)
- # beginners (35)
- # biff (2)
- # calva (5)
- # cider (10)
- # clara (11)
- # clerk (114)
- # clj-kondo (18)
- # cljdoc (37)
- # clojars (7)
- # clojure (24)
- # clojure-austin (10)
- # clojure-europe (27)
- # clojure-nl (1)
- # clojure-norway (23)
- # clojure-uk (2)
- # clojurescript (18)
- # conjure (2)
- # core-async (6)
- # cursive (21)
- # datomic (3)
- # fulcro (15)
- # introduce-yourself (7)
- # lsp (32)
- # malli (57)
- # meander (5)
- # music (1)
- # nbb (2)
- # off-topic (17)
- # pathom (6)
- # rdf (4)
- # reagent (8)
- # releases (2)
- # shadow-cljs (4)
- # slack-help (23)
- # spacemacs (6)
- # tools-build (32)
Api-docs at https://cljdoc.org/d/com.fulcrologic/fulcro/3.6.0-RC5/doc/readme have a build failure
Hm, don’t we have GH action checking that? Or does it only run on pull requests? Oh yeah, https://github.com/fulcrologic/fulcro/blob/main/.github/workflows/test.yml#L3. Perhaps we should enable it on push to master as well?
Though then I realized that for this use (logout), there's state I'd need to reset all over the place
There are some other helpers in the normalized state namespace. For example I think there are some garbage collection functions in there
For now I just force a page reload, until I get some good ideas how to make sure that Something still doesn't have dangling state left from whatever was there before the logout
Oh, for a log out, you can just do a reset of the state atom from get initial state, then reinitialize your routers etc
Of course that doesn't fix any stateful things you might have that are not in the state Atom