This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-23
Channels
- # admin-announcements (6)
- # aleph (3)
- # beginners (38)
- # boot (119)
- # braid-chat (15)
- # braveandtrue (1)
- # clara (4)
- # cljs-dev (56)
- # cljsfiddle (12)
- # cljsjs (15)
- # cljsrn (6)
- # clojars (4)
- # clojure (113)
- # clojure-art (1)
- # clojure-berlin (1)
- # clojure-dusseldorf (3)
- # clojure-india (15)
- # clojure-new-zealand (3)
- # clojure-poland (1)
- # clojure-russia (83)
- # clojure-uk (18)
- # clojurescript (97)
- # community-development (9)
- # cursive (1)
- # data-science (1)
- # datomic (12)
- # emacs (14)
- # hoplon (350)
- # immutant (2)
- # jobs (2)
- # jobs-discuss (23)
- # keechma (74)
- # liberator (1)
- # off-topic (1)
- # om (127)
- # onyx (54)
- # parinfer (74)
- # pedestal (1)
- # proton (5)
- # re-frame (6)
- # reagent (4)
- # remote-jobs (17)
- # ring-swagger (1)
- # slack-help (5)
- # untangled (16)
- # yada (21)
@josh.freckleton: handlers can take many arguments, you could write a generic handler like
(dispatch [:query-remote-db db-ref :users-table “123"
look at what would be varying if you were to write a handler for each resource, then make them parameters in one or a few handlers
@danielcompton: great advice, I'll do something like that
is there any prior work around making an app-db's timeline traversable, maybe with diffs? i.e. I hit Save in my app, a few things happen. Is there a way to send the value the app-db is holding someplace where I can inspect it and look through it?
oh and @danielcompton listening to your episode of Decompress
! (https://www.decompress.in/episodes/4/)
@escherize: there is undo, you could do something with inspecting the undo values? Or just take a copy of app-db and store it somewhere?