Hey, I am wondering if the unresolved symbol in the destructuring of the following example is intended ?

(defn foo [x {:keys [y] :or {y x}}]
  (list x y))

(ns foobar
  {:clj-kondo/config {}}
  (:require [ :as io]))

(ns foobar
  #_{:clj-kondo/config {}}
  (:require [ :as io]))

I don't see an existing issue for this, shall I go ahead and create one @borkdude?

Never mind. I updated to the most recent clj-kondo version and the problem went away!

(FYI, the above bug was in the 2020.04.05 version)

@seancorfield Could be an issue with parsing the clj-kondo config. Before it expected quotes like

{:clj-kondo/config '{}}

{:clj-kondo/config {}}

Note that

(ns foobar
  {:clj-kondo/config 1}
  (:require [ :as io]))

@borkdude I had ' in the real code example. What I posted was just the minimal example of the bug (which has clearly since been fixed).

It was definitely parsing the config correctly: it contained a :lint-as and without the form, Kondo flagged every use of that macro as an error.

I didn't realize I was on such an old version of Kondo.

Hope you are enjoying the new one

(I'm refactoring old test code right now so Kondo is helping me cleanup ns forms as I swap out uses of an old lib for uses of a new one!)

@seancorfield I think the most exciting new features since 2020.04.05 are hook support (for handling weird macros that don't work with :lint-as) and linting for clojure.core/format.

And a whole bunch of tiny fixes.

The thing you did for jdbc can now be done in user-land using hooks. The hooks are evaluated using sci (because a GraalVM binary cannot clojure.core/eval).

Yeah, I haven't had time to look at hooks yet, but they look very interesting.

At the moment it's probably mostly used by Rum users

Here's some examples: https://github.com/borkdude/clj-kondo/tree/master/examples/