This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-15
Channels
- # aleph (24)
- # announcements (8)
- # babashka (27)
- # beginners (55)
- # biff (4)
- # calva (32)
- # cider (5)
- # clj-kondo (11)
- # clojure (59)
- # clojure-android (3)
- # clojure-australia (1)
- # clojure-belgium (6)
- # clojure-dev (21)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-norway (17)
- # clojurescript (19)
- # css (1)
- # data-science (10)
- # datahike (17)
- # events (3)
- # figwheel-main (4)
- # honeysql (1)
- # hugsql (5)
- # hyperfiddle (1)
- # jobs (1)
- # leiningen (3)
- # lsp (6)
- # malli (5)
- # meander (4)
- # nbb (6)
- # off-topic (87)
- # pathom (19)
- # portal (2)
- # re-frame (4)
- # reitit (6)
- # releases (1)
- # remote-jobs (3)
- # shadow-cljs (29)
- # sql (8)
- # tools-deps (6)
- # xtdb (7)
Seems like clojure.test.check.clojure-test/defspec
should lint correctly without extra config.
Also the spec name gets added to the namespace as a callable function, which should ideally not be considered unresolved. (defspec my-spec ...) (my-spec 20) ; => a quick-check result
How would clj-kondo know that if you don't tell it how defspec
works? (unless it's built-in to clj-kondo which very few libraries are)
There is one piece of support in clj-kondo for clojure.test.check: the for-all macro. Maybe we should add support for defspec too, but since it isn't there, your best bet is probably :lint-as {clojure.test.check.clojure-test/defspec clj-kondo.lint-as/def-catch-all}
for now. Maybe we should add it to https://github.com/clj-kondo/configs
> The test.check
library is built into Clojure itself to support this
This isn't true though, test.check is not a library that comes with Clojure