This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-21
Channels
- # announcements (9)
- # beginners (222)
- # boot (11)
- # calva (40)
- # cider (1)
- # clj-kondo (10)
- # cljs-dev (1)
- # cljsrn (8)
- # clojars (4)
- # clojure (50)
- # clojure-dev (4)
- # clojure-ecuador (1)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-madison (2)
- # clojure-nl (26)
- # clojure-spec (86)
- # clojure-uk (34)
- # clojurescript (11)
- # clr (1)
- # cursive (46)
- # datomic (19)
- # emacs (4)
- # events (1)
- # fulcro (22)
- # graalvm (4)
- # graphql (2)
- # jobs-discuss (40)
- # leiningen (10)
- # luminus (6)
- # nrepl (7)
- # off-topic (18)
- # onyx (6)
- # overtone (1)
- # pedestal (2)
- # planck (1)
- # re-frame (5)
- # reagent (3)
- # reitit (8)
- # rewrite-clj (2)
- # shadow-cljs (139)
- # sql (4)
- # tools-deps (42)
here is a slightly interesting case: I deleted some braces from the end of an edn file:
$ clj-kondo --lint src/test/.clj-kondo/config.edn
src/test/.clj-kondo/config.edn:0:0: error: can't parse src/test/.clj-kondo/config.edn, Unexpected EOF. [at line 5, column 1]
The error is flagged as row/col 0:0, but the error message says 5:1
{:linters {
:invalid-arity {:level :error
This is somewhere were I really dislike the Clojure error message - it focuses on the wrong thing.
“Unexpected EOF” should be “unclosed {
at line 4 column 21"
yeah, good point. I though I parsed that exception somewhere and turned it into the correct locations, but it might not work everywhere. I’ll make an issue
https://github.com/borkdude/clj-kondo/issues/286 I’m not sure if “unclosed” will work, because this exception comes from tools.reader