This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-18
Channels
- # admin-announcements (10)
- # boot (260)
- # cider (44)
- # clojure (226)
- # clojure-berlin (24)
- # clojure-dev (68)
- # clojure-germany (5)
- # clojure-india (14)
- # clojure-italy (3)
- # clojure-japan (21)
- # clojure-poland (34)
- # clojure-russia (20)
- # clojure-spain (2)
- # clojure-uk (8)
- # clojurescript (86)
- # core-async (38)
- # core-typed (70)
- # datomic (41)
- # docs (8)
- # editors (7)
- # euroclojure (6)
- # instaparse (2)
- # jobs (8)
- # ldnclj (47)
- # om (17)
- # other-lisps (1)
- # reactive (1)
- # reading-clojure (8)
- # reagent (13)
- # sneer (1)
- # sneer-br (1)
Do people tend to use reagent-utils/session, or like to pass around an app object explicitly?
I feel like session is just a nice wrapper for a global variable, with lots of the potential foibles.
Is this the right place to ask about reagent frameworks like re-frame?
I'm having a hard time structuring reusable components with re-frame.
@petrus: what's issues do you experience with that? I'm curious because I'm sinking my teeth into it just about right now.
@petrus: have you looked at re-com? It works with re-frame.
yeah, none of the components seem to be nested components, though.
Nested components?
I have to head off, but look at the way re-com components are written. We don't have any problem mixing re-com and re-frame.
regarding re-com - is allowing only goog.date.UtcDateTime as input for datepicker's 'model' intentional? or was goog.date.DateTime overlooked?