This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-26
Channels
- # aws (7)
- # beginners (109)
- # boot (5)
- # carry (2)
- # cider (25)
- # clara (6)
- # cljs-dev (86)
- # cljs-experience (19)
- # cljsrn (1)
- # clojure (183)
- # clojure-dev (7)
- # clojure-dusseldorf (7)
- # clojure-gamedev (2)
- # clojure-greece (32)
- # clojure-italy (2)
- # clojure-norway (1)
- # clojure-russia (228)
- # clojure-sg (3)
- # clojure-spec (38)
- # clojure-uk (104)
- # clojurebridge (1)
- # clojurescript (29)
- # community-development (9)
- # core-async (118)
- # core-matrix (20)
- # cursive (5)
- # datomic (140)
- # emacs (25)
- # figwheel (1)
- # hoplon (21)
- # jobs (4)
- # lein-figwheel (2)
- # luminus (10)
- # lumo (35)
- # off-topic (137)
- # om (31)
- # onyx (62)
- # pedestal (6)
- # reagent (25)
- # remote-jobs (1)
- # ring-swagger (11)
- # spacemacs (2)
- # test-check (17)
- # uncomplicate (10)
- # unrepl (1)
- # untangled (20)
- # vim (4)
- # yada (3)
@chancerussell https://anmonteiro.com/2016/02/routing-in-om-next-a-catalog-of-approaches/ perhaps?
Hi. Is anybody using om-next with datascript ? Trying to figure out if it’s worth the learning curve & if there are downsides to using it instead of an atom.
The downside (if you consider it one) is that set-query!
won't work and you'll have to implement your own merge function (if dealing with a remote).
it’s still in alpha, but i think it’s pretty close to a beta release. let me find the message
@dnolen gonna upgrade React in master before that, sounds good?
@anmonteiro sounds great
awesome
I’ve just created an om-cljs Google Group https://groups.google.com/d/forum/om-cljs
nothing to see there yet, but it’ll be nice to have a place for discussion outside of Slack
just bumped some deps in master, most importantly React to 15.5.4
Many people will be excited about Beta arrival. Thanks to whole team who've made Om and Om-Next such great tools to help us make great software.
And a special Thx to David for his original idea and then not settling on good enough. Your stewardship has helped us all.
README will be overhauled, and I think we should take the same strategy as Clojure(Script) for docs, sans the CA requirement for docs
I’d particularly like to see what you had in mind for the error stuff
@anmonteiro yeah will have to come later, needs more hammock 🙂