This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-26
Channels
- # announcements (3)
- # babashka (23)
- # beginners (54)
- # calva (9)
- # cider (8)
- # clj-kondo (18)
- # cljsrn (25)
- # clojure (69)
- # clojure-australia (1)
- # clojure-europe (7)
- # clojure-spec (13)
- # clojure-uk (1)
- # clojurescript (122)
- # conjure (8)
- # cursive (15)
- # defnpodcast (9)
- # deps-new (2)
- # emacs (22)
- # fulcro (10)
- # graalvm (36)
- # luminus (5)
- # meander (5)
- # minimallist (1)
- # observability (6)
- # off-topic (54)
- # reagent (8)
- # reitit (2)
- # releases (1)
- # reveal (25)
- # shadow-cljs (21)
- # tools-deps (50)
- # vrac (1)
- # xtdb (2)
so what's up w/ calva and clj-kondo ignoring (use..
statements and throwing out all unresolved symbols?
I ran clj-kondo --parallel --lint "$(lein classpath)"
and that seemed to generate a cache for most things, but any symbol that comes out of a use
is not picked up and is in red as unknown
it's closed source, but looks like I have a handful of use
and a few :refer :all
that result in unknown symbols... there's nothing special about them - mainly a bunch of pure functions for logging or string manipulation
Lein isn't part of the picture. clj-kondo runs in a separate process, using only static analysis. I think that the only thing that would really help is a repro.
@clypto There's a related open issue about this: https://github.com/borkdude/clj-kondo/issues/1010 I'll look into this soon, maybe it will fix your issue as well. The best for now is to get rid of use and refer :all altogether, which is best practice anyway