This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-07
Channels
- # adventofcode (114)
- # announcements (3)
- # aws (5)
- # babashka (62)
- # beginners (111)
- # calva (4)
- # cider (20)
- # clara (5)
- # clj-kondo (1)
- # cljs-dev (9)
- # clojure (255)
- # clojure-europe (75)
- # clojure-italy (10)
- # clojure-nl (3)
- # clojure-norway (5)
- # clojure-uk (6)
- # clojuredesign-podcast (5)
- # clojurescript (34)
- # community-development (28)
- # conjure (1)
- # cursive (3)
- # data-science (1)
- # datavis (1)
- # datomic (4)
- # figwheel-main (1)
- # fulcro (14)
- # graalvm (1)
- # graphql (8)
- # integrant (4)
- # introduce-yourself (2)
- # jobs (2)
- # juxt (4)
- # kaocha (2)
- # malli (6)
- # membrane-term (53)
- # mount (2)
- # nextjournal (2)
- # off-topic (27)
- # pathom (11)
- # polylith (3)
- # portal (11)
- # reagent (4)
- # reitit (4)
- # remote-jobs (1)
- # reveal (14)
- # shadow-cljs (22)
- # tools-deps (24)
- # vim (6)
- # xtdb (19)
Hi! Is it possible to make Cursive/II report an error when I have an unused alias? I do not see this particular inspection in Prefs - Editor - Inspections - Clojure (there is "unused require" but changing that to Error has on visible effect). I want to be loudly informed when I have an unused require/alias so that I can fix it before it fails on CI 🙏
I guess IntellliJ needs to have a “loudly” inform feature for that. You can click on the problems tab to see the issues. If you’re using IntelliJ to commit your files you could turn on Analyze Code to not allow you to commit unless all the problems are resolved. Or alternatively you could add clj-kondo to your git pre-commit hooks.
Thank you!