This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-23
Channels
- # admin-announcements (2)
- # arachne (2)
- # beginners (76)
- # boot (241)
- # cider (14)
- # cljsrn (2)
- # clojars (3)
- # clojure (94)
- # clojure-android (12)
- # clojure-dev (33)
- # clojure-gamedev (1)
- # clojure-greece (3)
- # clojure-india (1)
- # clojure-nl (2)
- # clojure-quebec (3)
- # clojure-russia (21)
- # clojure-spec (38)
- # clojure-uk (72)
- # clojurescript (62)
- # cursive (20)
- # datascript (3)
- # datomic (14)
- # devcards (1)
- # dirac (14)
- # emacs (11)
- # hoplon (7)
- # jobs (2)
- # keechma (1)
- # lein-figwheel (9)
- # leiningen (9)
- # luminus (1)
- # off-topic (6)
- # om (13)
- # onyx (30)
- # planck (181)
- # proton (3)
- # re-frame (6)
- # reagent (6)
- # specter (108)
- # spirituality-ethics (7)
- # untangled (3)
I was thinking I could create my own undo-stack by pushing states upon each mutation except for the undo itself, but there might be a cleaner way..?
@nxqd: I switched from params using set-query to putting it in app-state, can highly recommend it
@mitchelkuijpers: still it would be interesting to know the cases where set-query
/ IQueryParams
is a good choice. My mental picture at the moment has 'none' in that category. But that must be wrong.
@cjmurphy: I agree.. Maybe for a autocomplete like in the tutorial?
@mitchelkuijpers: I can see that it works perfectly fine and reasonable clean in simple example. but the more componentes involved it gets out of hand pretty quickly ...
@nxqd: do you mean putting it in the app-state or using params?
Aha yes i cannot recommend that
From the #C0PULSD25 channel. I've been making a number of videos for getting started with Untangled (which uses Om underneath). A number of the topics and solutions are pretty Om-centric, so even those that want to use raw Om can pick up a thing or two. If you like learning from video, check them out: https://www.youtube.com/playlist?list=PLVi9lDx-4C_T_gsmBQ_2gztvk6h_Usw6R