This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-10
Channels
- # asami (41)
- # babashka (24)
- # beginners (48)
- # calva (41)
- # cider (10)
- # clj-commons (20)
- # clj-kondo (2)
- # cljdoc (8)
- # clojure (131)
- # clojure-australia (4)
- # clojure-europe (17)
- # clojure-hungary (2)
- # clojure-india (2)
- # clojure-nl (3)
- # clojure-uk (1)
- # clojurescript (12)
- # community-development (6)
- # core-logic (4)
- # cursive (11)
- # datomic (22)
- # emacs (25)
- # events (1)
- # exercism (2)
- # fulcro (30)
- # helix (5)
- # honeysql (6)
- # hugsql (3)
- # integrant (12)
- # introduce-yourself (4)
- # lsp (5)
- # malli (5)
- # nextjournal (31)
- # off-topic (4)
- # pedestal (3)
- # portal (51)
- # reitit (33)
- # remote-jobs (1)
- # shadow-cljs (12)
- # sql (10)
- # vim (7)
- # xtdb (37)
i wonder if it would be possible to get hugsql play nice with clj-kondo out of the box, so that projects wouldn't need to suppress warnings or add extra namespaces?
@shem this would require clj-kondo to parse the .sql files to see which vars are in them. you can also just add the hugsql namespaces to be excluded in unresolved vars: {:linters {:unresolved-var {:exclude [foo]}}}
we have lots of namespaces using hugsql, it would be a pity to lose the unresolved-var warning in all of them, and also quite tedious to keep the exclusion list up to date. well, it's quite obvious to see from our naming conventions which warnings concern hugsql and are spurious, we can live with that