This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-04
Channels
- # announcements (1)
- # babashka (41)
- # beginners (124)
- # cider (8)
- # clj-kondo (25)
- # cljs-dev (40)
- # clojars (4)
- # clojure (92)
- # clojure-europe (35)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-uk (91)
- # clojuredesign-podcast (8)
- # clojurescript (41)
- # code-reviews (1)
- # cursive (11)
- # data-science (1)
- # datascript (76)
- # datomic (45)
- # emacs (4)
- # etaoin (3)
- # events (1)
- # figwheel-main (2)
- # fulcro (9)
- # graalvm (1)
- # jackdaw (6)
- # jobs (1)
- # jobs-discuss (3)
- # kaocha (4)
- # malli (25)
- # off-topic (42)
- # pathom (4)
- # reitit (11)
- # releases (2)
- # reveal (1)
- # shadow-cljs (53)
- # sql (4)
- # tools-deps (190)
- # vrac (19)
- # xtdb (6)
Hi, any plans on splitting the jackdaw library into more fine grained libraries? I would love to be able to use parts of the jackdaw library but not having all the dependencies. E.g jackdaw.streams could be it's own library 🙂
hehe, that's how it was originally organized before we released it. The problem was it was a pain when it came to update time.
I see. I'll look into excluding deps, didn't think about it - thanks! ✌️
Hey @daniel415, I think that's not possible due to the fact that the serde mechanism in kafka streams has it's own class path resolver that doesn't know about "anonymous" classes generated on the fly by clojure. You could workaround this problem by wrapping the json serde the same way it's done in the edn serde.