This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-29
Channels
- # announcements (35)
- # aws (40)
- # babashka (10)
- # beginners (119)
- # calva (25)
- # cider (13)
- # clj-kondo (15)
- # cljsrn (23)
- # clojure (205)
- # clojure-dev (3)
- # clojure-europe (15)
- # clojure-germany (3)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-uk (58)
- # clojurescript (193)
- # community-development (2)
- # conjure (147)
- # core-async (49)
- # cursive (47)
- # datomic (27)
- # duct (1)
- # fulcro (19)
- # graalvm (3)
- # graphql (1)
- # helix (3)
- # hoplon (11)
- # jackdaw (1)
- # joker (1)
- # juxt (5)
- # kaocha (1)
- # keechma (3)
- # lambdaisland (6)
- # local-first-clojure (27)
- # malli (5)
- # off-topic (41)
- # rdf (27)
- # re-frame (7)
- # reagent (15)
- # reitit (5)
- # rum (11)
- # shadow-cljs (157)
- # spacemacs (18)
- # sql (4)
- # xtdb (8)
If you use Stuart Sierra's Component library with next.jdbc
, I've just added some experimental out-of-the-box support for it (without next.jdbc
requiring it as a dependency so it won't affect anyone who doesn't use Component!): https://github.com/seancorfield/next-jdbc/commit/66fdba4be9a80a85d5fc75df0a2341820b10fa22
Nice! If I understand correctly, you're using "extend via metadata" to extend the protocol without adding a dependency on the package the protocol is defined in?
Correct. If your project doesn't include Component, this feature doesn't do anything useful.
The expected usage is provided in the comment
form. I'll document it fully before cutting the next release.