This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-16
Channels
- # adventofcode (36)
- # announcements (30)
- # babashka (1)
- # beginners (161)
- # boot-dev (2)
- # bristol-clojurians (3)
- # clj-kondo (10)
- # clojure (125)
- # clojure-europe (10)
- # clojure-italy (4)
- # clojure-nl (7)
- # clojure-spec (1)
- # clojure-uk (26)
- # clojuredesign-podcast (3)
- # clojurescript (13)
- # core-async (5)
- # cryogen (3)
- # cursive (134)
- # data-science (8)
- # datascript (3)
- # datomic (32)
- # fulcro (24)
- # graalvm (2)
- # joker (5)
- # leiningen (5)
- # malli (18)
- # off-topic (14)
- # pathom (4)
- # re-frame (3)
- # reagent (11)
- # remote-jobs (3)
- # rewrite-clj (8)
- # shadow-cljs (47)
- # spacemacs (3)
- # sql (12)
- # vim (6)
@delaguardo I'm getting these 403s from the clojure lint action: https://github.com/borkdude/clj-kondo/pull/665/checks?check_run_id=351219419
According to documentation create-check-run should not be triggered from the push to the branch in a forked repository. Will try to find a workaround
Can't check right now. Already away from the keyboard. Will check that tomorrow morning.
Any suggestions on how best to handle linter errors/warnings when using next.jdbc/with-transaction
? One would think to lint-as clojure.core/with-open
, however this doesn’t work because with-transaction
supports an odd number of arguments in the initial vector and so you get uneven forms error. Example usage:
(next.jdbc/with-transaction [conn datasource options-map]
;; do stuff with conn
)
hmm, maybe just ignore the name conn
with {:linters {:unresolved-symbol {:exclude [(next.jdbc/with-transaction [conn])]}}}