This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-13
Channels
- # aleph (7)
- # announcements (3)
- # babashka (29)
- # beginners (70)
- # calva (5)
- # cider (14)
- # clara (3)
- # clj-kondo (25)
- # cljs-dev (2)
- # clojure (237)
- # clojure-conj (3)
- # clojure-europe (6)
- # clojure-italy (14)
- # clojure-nl (4)
- # clojure-uk (40)
- # clojurescript (29)
- # clojurex (1)
- # code-reviews (2)
- # cursive (3)
- # datascript (1)
- # fulcro (11)
- # graalvm (4)
- # graphql (12)
- # jackdaw (1)
- # jobs (1)
- # joker (22)
- # london-clojurians (1)
- # off-topic (132)
- # re-frame (38)
- # rewrite-clj (11)
- # shadow-cljs (200)
- # spacemacs (1)
- # sql (67)
- # tools-deps (15)
@fiddlerwoaroof Can be implemented, but probably low priority since it's not wrong and doesn't cost you any performance if you this.
@borkdude makes sense, I thought it was an interesting case, though, because it usually comes up for me after I've eliminated all the unused bindings from destructuring.
low priority doesn't mean "won't implement", you're still welcome to create an issue
I've been puzzling over a quirk in my workflow that affects clj-kondo, among other things, and I wonder what to do about it...
Basically I'm moving to always have my editor in ~/src, one level above my projects, to lower the barrier to project-switching and make some other things work.
This means that a projects' .clj-kondo/config.edn
isn't available by my editor's lint wrapper.
I can probably patch my editor's lint script. Hmm, I think that's actually the right thing to do.
@eraserhd One thing I've been thinking about when linting a single file (which is what you do with editor integration) is search down from the path of the linted file instead of the cwd
so when you lint /tmp/foo/bar/baz.clj and your cwd is /tmp/foo but your .clj-kondo is in /tmp/foo/bar, it would still work
oh neat. That would solve my problem, and since I would otherwise write a wrapper, I might as well make a PR for that.
that will also solve the problem in VSCode when you edit an "unrelated to the current workspace/dir" clojure file (not sure how common that is, cc @pez)
this sounds similar to the issue i was experiencing with running clj-kondo not from the project directory as root -- clj-kondo resolves paths based on user.dir, at least i think it used to
in my indexing program i resolved this by only handing absolute paths to clj-kondo's --lint
Would it still find a .clj-kondo
in /tmp/foo? And what does it do if there is a .clj-kondo
in both locations?
I don’t know about others, but i certainly quite often open up a clj file from somewhere random even when working with a project.