This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-09
Channels
- # aws (3)
- # babashka (48)
- # babashka-sci-dev (1)
- # beginners (143)
- # calva (62)
- # clj-kondo (6)
- # clj-otel (3)
- # cljs-dev (59)
- # cljsrn (4)
- # clojure (39)
- # clojure-austin (5)
- # clojure-europe (60)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-romania (4)
- # clojure-spec (3)
- # clojure-uk (2)
- # clojurescript (32)
- # datomic (17)
- # events (3)
- # figwheel-main (4)
- # graphql (3)
- # gratitude (2)
- # holy-lambda (52)
- # introduce-yourself (3)
- # jobs (1)
- # juxt (5)
- # kaocha (2)
- # lsp (33)
- # nyc (3)
- # off-topic (9)
- # other-languages (4)
- # overtone (1)
- # portal (21)
- # reitit (2)
- # remote-jobs (5)
- # shadow-cljs (65)
- # tools-deps (2)
- # xtdb (8)
Per the following PR, is there in fact a lightweight way to test linting contributions? https://github.com/lilactown/helix/pull/93#pullrequestreview-966414595
I think, in terms of providing confidence to maintainers during lint-related PRs, automated testing was probs the idea in mind. Might that involve consuming clj-kondo
as a lib and calling it upon hooks, etc?
Yes, linting the actually library and tests with 0 lint warnings would be the ultimate test, don't you think?
> https://clojurians.slack.com/archives/CHY97NXE2/p1652147809862699?thread_ts=1652132817.173779&cid=CHY97NXE2 Yes indeed, I had assumed for some reason you were suggesting just running it by hand via CLI, and didn't and still don't yet know what it means to use it as a JVM test lib, though this can be explored at @U4YGF4NGM’s discretion I suppose!