This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-07
Channels
- # aleph (4)
- # arachne (2)
- # aws (2)
- # beginners (42)
- # boot (4)
- # cider (47)
- # cljs-dev (352)
- # clojure (278)
- # clojure-dusseldorf (6)
- # clojure-italy (6)
- # clojure-russia (1)
- # clojure-spec (15)
- # clojure-uk (94)
- # clojurescript (197)
- # community-development (34)
- # cursive (3)
- # data-science (1)
- # datomic (64)
- # emacs (3)
- # figwheel (16)
- # fulcro (7)
- # hoplon (5)
- # jobs (3)
- # luminus (3)
- # mount (2)
- # nyc (1)
- # off-topic (31)
- # onyx (22)
- # parinfer (1)
- # protorepl (7)
- # re-frame (9)
- # reagent (61)
- # ring-swagger (3)
- # shadow-cljs (149)
- # spacemacs (18)
- # specter (4)
- # timbre (1)
- # unrepl (38)
- # vim (17)
- # yada (14)
@achikin What’s wrong with an interceptor that would add to the :db (if it exists) fx in :after?
@achikin https://gist.github.com/CalebMacdonaldBlack/a65b2f3ccee31bb7b8a574c0a1574374
I haven’t tested it so it might not work straight away.
Yes, I know that technique. My initial challenge was to make it more reactive e.g. you should not stick a callback/interceptor in every place where you update the data.
Yes, you're right. That's why I'm probably not going to use it in production code. Is there any way I can make it more like watcher without such tricks?
@achikin wouldn’t it also be possible to keep a separate copy of the form input in the db and then compare those two in a subscription to see if the form input has changed?
Yes, I'd probably take this path in the future. More generally speaking this leads to full-fledged undo functionality which is a bit overwhelming for me right now.