This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-12
Channels
- # aleph (1)
- # announcements (13)
- # asami (4)
- # babashka (47)
- # beginners (22)
- # calva (11)
- # circleci (1)
- # clj-kondo (14)
- # clojure (43)
- # clojure-europe (43)
- # clojure-gamedev (1)
- # clojure-nl (1)
- # clojure-uk (6)
- # clojurescript (13)
- # core-async (5)
- # cursive (8)
- # datomic (20)
- # events (3)
- # fulcro (12)
- # graalvm (1)
- # graphql (4)
- # gratitude (3)
- # java (2)
- # juxt (2)
- # leiningen (12)
- # off-topic (30)
- # pathom (33)
- # pedestal (5)
- # podcasts-discuss (1)
- # polylith (14)
- # rdf (2)
- # re-frame (12)
- # reagent (3)
- # releases (2)
- # shadow-cljs (24)
- # spacemacs (13)
- # sql (2)
- # tools-build (16)
I think you could already use the clj-kondo analysis for this if you want to script this yourself btw
👍 1
It could be a warning of multiple definitions, no needed to tell which one is overwriting the other.
clojure-lsp already provides navigation to specs using keywords (using the same analysis). perhaps it would be a small extra step for it.
yes. but because it already keeps track of these definitions, it can catch duplicates fairly easily and perhaps warn: this spec is also defined in another file
@U05094X3J feel free to create a issue about clojure-lsp warn about duplicate definitions, sane examples would help a lot
👍 1