This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-14
Channels
- # announcements (1)
- # beginners (13)
- # calva (2)
- # cider (43)
- # cljdoc (11)
- # clojure (16)
- # clojure-spec (10)
- # clojure-uk (6)
- # clojurescript (7)
- # code-reviews (3)
- # core-matrix (1)
- # datascript (4)
- # datomic (7)
- # devcards (4)
- # figwheel-main (12)
- # fulcro (27)
- # hoplon (1)
- # lein-figwheel (1)
- # luminus (1)
- # nrepl (23)
- # off-topic (4)
- # planck (1)
- # re-frame (8)
- # reagent (7)
- # shadow-cljs (61)
- # spacemacs (7)
- # tools-deps (19)
any recommendation for handling global keyboard events in a re-frame app? is https://github.com/gadfly361/re-pressed the way to go? i'm worried about pulling in all of jquery for cross-browser compatibility, isn't this why google closure library is bundled with cljs? plus tree-shaking with google closure is easier i assume...
@bravilogy I've generally followed that advice IIRC, starting with a flat directory structure with a single events
, subs
, and views
and splitting those into separate directory structures when complexity/size warrants it.
I'm interested in exploring the alternative touched on in https://purelyfunctional.tv/guide/database-structure-in-re-frame/ though, which is to have domain oriented namespaces, with events and subs (and views?) bundled together. Maybe on my next project. 🙂
I split by domains and use namespaced keywords for everything
So you can always easily see where an event is defined
oh definitely namespaced keywords, that's a huge win for someone else reading the codebase
events, subs and views bundled together + namespaced keywords works for me