This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-24
Channels
- # adventofcode (2)
- # anglican (1)
- # announcements (4)
- # aws (2)
- # babashka (28)
- # beginners (18)
- # brompton (3)
- # calva (22)
- # clj-kondo (2)
- # cljdoc (29)
- # clojure (41)
- # clojure-europe (28)
- # clojure-gamedev (14)
- # clojure-nl (2)
- # clojure-spec (2)
- # clojure-sweden (1)
- # clojure-uk (6)
- # clojurescript (53)
- # css (3)
- # cursive (6)
- # duct (3)
- # emacs (5)
- # fulcro (29)
- # introduce-yourself (1)
- # liberator (5)
- # lsp (1)
- # malli (11)
- # meander (4)
- # nbb (11)
- # off-topic (17)
- # pathom (2)
- # polylith (8)
- # practicalli (1)
- # react (6)
- # reagent (11)
- # releases (2)
- # rewrite-clj (11)
- # shadow-cljs (59)
- # tools-deps (21)
- # vim (11)
I'd swear I saw some reagent page discussing spec, but I can't find it. Seems good to formalize a bit what's in the state atom, but not sure how to do so elegantly without adding a ton of overhead.
Not sure I follow.
"What's in the state atom" - what do you mean by that? How r/atom
works or what users of Reagent should put in their ratoms?
Well I have a r/atom with a bunch of stuff, and I'd like to formalize a bit what goes where.
What do you mean by "formalize"? Some textual description of what components should store in their state in general, same but for specific components, or maybe something that's checked at run time, maybe something else?
Using clojure.spec
I am updating my state on mouse-move though, so it'd add a bunch of overhead. Maybe I'll do that during development and only check in a few key places in production.
hmmm is there some utility for that? Or it'd be some hack with settimeout or something