We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version v2021.10.19
platform native
problem type-mismatch is indicating missing required keys when the keys are in fact present, but have aliased namespaces.
type-mismatch
repro /tmp/lint-test.clj
/tmp/lint-test.clj
(ns test-ns (:require [some-ns :as s])) (defn- x [y] y) (x {::s/thing 1}) (x #::s{:thing 1}) (x {:some-ns/thing 1})
/tmp/lint-test-config.edn
{:linters {:type-mismatch {:namespaces {test-ns {x {:arities {1 {:args [{:op :keys, :req {:some-ns/thing :any}}]}}}}}}}}
$ cat /tmp/lint-test.clj | clj-kondo --lint - --config /tmp/lint-test-config.edn . <stdin>:6:4: error: Missing required key: :some-ns/thing linting took 36ms, errors: 1, warnings: 0
expected behavior Lines 6, 7, and 8 should be equivalent and result in no errors overall, but line 6 is treated differently.
I assume this is related to code modified in #1251, but I could be wrong.
The text was updated successfully, but these errors were encountered:
Note to self: so only the (x {::s/thing 1}) one is failing.
(x {::s/thing 1})
Sorry, something went wrong.
[#1467] Fix type mismatch error with auto-qualified keyword
16c0d4d
[#1467] Fix type mismatch error with auto-qualified keyword (#1470)
41b9346
Fixed on master.
No branches or pull requests
version v2021.10.19
platform native
problem
type-mismatch
is indicating missing required keys when the keys are in fact present, but have aliased namespaces.repro
/tmp/lint-test.clj
/tmp/lint-test-config.edn
expected behavior
Lines 6, 7, and 8 should be equivalent and result in no errors overall, but line 6 is treated differently.
I assume this is related to code modified in #1251, but I could be wrong.
The text was updated successfully, but these errors were encountered: