This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-03
Channels
- # announcements (63)
- # asami (29)
- # beginners (23)
- # calva (23)
- # cider (18)
- # clj-kondo (12)
- # clojure (156)
- # clojure-europe (30)
- # clojure-italy (6)
- # clojure-nl (5)
- # clojure-uk (6)
- # clojurescript (14)
- # conjure (26)
- # cursive (8)
- # datalog (143)
- # datascript (1)
- # datomic (6)
- # duct (2)
- # emacs (50)
- # events (4)
- # figwheel-main (6)
- # fulcro (7)
- # graphql (12)
- # jobs (6)
- # malli (1)
- # mid-cities-meetup (2)
- # off-topic (4)
- # pathom (6)
- # portal (7)
- # re-frame (10)
- # reagent (8)
- # reitit (10)
- # releases (1)
- # reveal (18)
- # shadow-cljs (39)
- # sql (4)
- # tools-deps (36)
- # vim (25)
- # xtdb (6)
Hey, is the current intention for users of clj-kondo to copy and paste the hook definitions of libraries into each project using those definitions? E.g copying hooks/slingshot if using Slingshot?
@charliebriggs Currently, yes
If you found something in the READMEs confusing about this, please let me know and I'll change it
great, I think it would help if that was more explicit in the Libraries
section, i.e. directly calling out the process of adding them for now
something like:
> Configuration for external libraries can be setup in each clj-kondo project by copying the required library configuration into the .clj-kondo
directory. See libraries
for a collection of existing configurations
I have wondered if using a different name like reference-config
or something would be clearer
cool, is there any way for libraries to package these configurations currently which can then be picked up by clj-kondo, or is something like that on the roadmap?
@charliebriggs It is something I've been thinking about and there is an issue for it. https://github.com/borkdude/clj-kondo/issues/559 It's just not that clear cut yet.
great, thanks for your help!