This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-02
Channels
- # announcements (37)
- # babashka (9)
- # beginners (172)
- # calva (7)
- # cestmeetup (28)
- # chlorine-clover (27)
- # clj-kondo (2)
- # cljs-dev (45)
- # cljsrn (8)
- # clojure (185)
- # clojure-dev (27)
- # clojure-europe (6)
- # clojure-finland (3)
- # clojure-nl (5)
- # clojure-uk (13)
- # clojuredesign-podcast (4)
- # clojurescript (54)
- # conjure (19)
- # core-typed (1)
- # cursive (40)
- # datomic (9)
- # emacs (5)
- # figwheel-main (34)
- # fulcro (238)
- # graphql (14)
- # hugsql (3)
- # leiningen (4)
- # malli (6)
- # off-topic (12)
- # pedestal (5)
- # portkey (19)
- # protorepl (8)
- # rdf (2)
- # re-frame (23)
- # reagent (3)
- # reitit (16)
- # shadow-cljs (29)
- # spacemacs (12)
- # sql (1)
- # xtdb (15)
I hope I said this right about VSCode / Calva: https://stackoverflow.com/questions/61752908/how-to-point-calva-clj-kondo-to-find-the-config-file-in-a-subrepo-not-at-root
I’m not sure how the clj.kondo extension works here. And also not sure what the monorepo workflow really looks like. But it might be that the clj-kondo extensions needs to provide a setting for where to find the config file.
I’m not sure why someone wouldn’t want the linting config in the root. But this happens to me when I have several repos open in workspace, their independent linting configs aren’t used
yes, it's because the current working directory of the plugin is determined by one of those repos
I fixed this issue with https://github.com/borkdude/clj-kondo/issues/907