This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-20
Channels
- # aleph (2)
- # boot (18)
- # cider (3)
- # cljs-dev (14)
- # cljsrn (28)
- # clojure (428)
- # clojure-austin (3)
- # clojure-hk (1)
- # clojure-ireland (5)
- # clojure-mexico (1)
- # clojure-quebec (2)
- # clojure-russia (49)
- # clojure-spec (138)
- # clojure-uk (45)
- # clojurescript (70)
- # core-async (1)
- # cursive (8)
- # datomic (13)
- # defnpodcast (3)
- # devops (1)
- # editors (4)
- # events (1)
- # funcool (14)
- # hoplon (17)
- # jobs-rus (1)
- # luminus (5)
- # mount (51)
- # off-topic (21)
- # om (9)
- # om-next (8)
- # onyx (43)
- # planck (6)
- # re-frame (13)
- # reagent (18)
- # ring-swagger (1)
- # spacemacs (17)
- # untangled (18)
- # vim (13)
- # yada (21)
anyone know of a good example of a “large application” built with re-frame? I know about the relevant wiki section
@miguelb: i've got a 40kloc app, with about ~18kloc in re-frame/cljs ... dunno if that counts as large !
Working with a re-frame app right now and I was looking for examples on how others have structured their large apps
i've tried a few different things - the approach which is sticking is to divide the app into components and areas, and give each of those things its own [subs / handlers / views] namespaces, carving those namespaces up themselves when they become unwieldy, so e.g. having app.components.infinite-scroll.subs
app.components.infinite-scroll.handlers
app.components.infinite-scroll.views
namespaces
i haven't done that - though i have split out the schema definitions into the components
do you have situations where a view in a one “component” namespace must dispatch an event in another namespace? (for example in app.components.widget_a.view
dispatches :widget_b/something
) If you do, does widget_b
handler’s ns have the handler?
ah, sometimes i have the notion of an empty
component and functions to create those structures for app-db are also split out, so i guess my app-db is a little split, though not greatly
yeah, it's not uncommon for one area to dispatch an event handled by another area. it hasn't happened often enough for me to have formalised it yet though