This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-06
Channels
- # announcements (14)
- # babashka (12)
- # beginners (61)
- # biff (2)
- # calva (16)
- # clj-kondo (22)
- # cljdoc (7)
- # clojure (131)
- # clojure-europe (52)
- # clojure-losangeles (9)
- # clojure-norway (54)
- # clojure-spec (5)
- # clojure-uk (4)
- # clojurescript (18)
- # cursive (14)
- # datomic (19)
- # deps-new (14)
- # emacs (8)
- # events (7)
- # fulcro (6)
- # graphql (3)
- # hyperfiddle (42)
- # instaparse (5)
- # lsp (10)
- # malli (21)
- # nbb (1)
- # off-topic (3)
- # pathom (3)
- # polylith (7)
- # reagent (14)
- # releases (2)
I have a couple vars that shadow clojure.test function names (`testing` primarily), and if i try to use the code action to automatically add the import when i've written (testing ...)
, it only shows me Add require '[clojure.test :refer [testing]]
, even tho I have the file that defines my personal testing
open in another tab and I know that LSP has cached its references. are these hardcoded? can that be relaxed?
it looks like it should be selecting the right one, so i'm not sure what's happening
hum, interesting, yeah, we have common-symbols pre-defined and we try to find there first https://github.com/clojure-lsp/clojure-lsp/blob/57d39a0c31b733f5c71d7f33265cad39e23bed6b/lib/src/clojure_lsp/feature/add_missing_libspec.clj#L458
but would be nice to support your case, I wonder if we can just always check the analysis since it's pretty consistent nowadays
I don't even mind it suggesting clojure.test, i'd just like it to suggest both, you know?
want a github issue?