This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-22
Channels
- # aleph (5)
- # announcements (9)
- # babashka (9)
- # beginners (127)
- # cherry (1)
- # cider (48)
- # clj-kondo (5)
- # cljdoc (1)
- # clojure (70)
- # clojure-berlin (1)
- # clojure-europe (57)
- # clojure-france (2)
- # clojure-germany (1)
- # clojure-nl (2)
- # clojure-norway (4)
- # clojure-uk (1)
- # clojurescript (2)
- # css (1)
- # cursive (6)
- # emacs (6)
- # gratitude (1)
- # honeysql (5)
- # introduce-yourself (5)
- # jobs-discuss (7)
- # joyride (1)
- # kaocha (3)
- # lsp (1)
- # malli (9)
- # nbb (2)
- # off-topic (91)
- # pathom (7)
- # pedestal (14)
- # re-frame (4)
- # reitit (67)
- # shadow-cljs (46)
- # spacemacs (3)
- # squint (3)
- # tools-build (14)
- # tools-deps (1)
- # vim (3)
Do you ever run into the issue where you've overridden a dep from the main :deps
list in :extra-deps
in an alias with a locally checked out version? Usually lsp still looks at the original one, which gets messed up if any changes happen in the local version.
if you don't restart lsp via lsp-workspace-restart
, clojure-lsp will use the old classpath, did you restart it?
I don't think that's the reason because my project has been set up like that long-term as I develop a group of libraries in parallel.
if you manage to create a simple repro where I can test maybe we could find the reason, it could be a bug somewhere
Ok, I'll do that, but may be a bit of time before I can get to it.