This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-10
Channels
- # aleph (4)
- # aws (2)
- # bangalore-clj (2)
- # beginners (84)
- # boot (25)
- # cider (3)
- # cljsrn (3)
- # clojure (57)
- # clojure-italy (5)
- # clojure-losangeles (3)
- # clojure-russia (7)
- # clojure-spec (18)
- # clojure-uk (29)
- # clojurescript (90)
- # cursive (11)
- # data-science (68)
- # datascript (2)
- # datomic (25)
- # duct (3)
- # fulcro (13)
- # graphql (7)
- # immutant (1)
- # jobs (1)
- # leiningen (12)
- # lumo (1)
- # off-topic (51)
- # om (43)
- # onyx (15)
- # parinfer (10)
- # pedestal (4)
- # re-frame (7)
- # reagent (42)
- # ring-swagger (42)
- # rum (1)
- # shadow-cljs (172)
- # spacemacs (10)
- # specter (4)
- # sql (4)
- # test-check (19)
- # unrepl (54)
- # yada (3)
> I like the idea of supporting combining key values via multimethods, as then custom behaviour can be defined that depends on the key. @weavejester ok so something like?
(derive :foo.bar/merge-key :duct.core/merge-key)
(defmethod :foo.bar/vector-merge-key [& vecs]
(apply concat vecs)
not sure if the derive is necessary; but was thinking it might be useful to be able to identify merge-keys. Could potentially wrap up in a defmergekey
macro, to help make intent more explicit.
@weavejester the duct profile idea seem interesting. How are they different to include? Curious to hear more about how they might work…