Fork me on GitHub
#clj-kondo
<
2019-11-16
>
bringe00:11:35

Hello. I have a quick question: Does clj-kondo know how to handle function args in var metadata?

bringe00:11:46

It appears not, but maybe I'm missing something

bringe17:11:33

Awesome! Thanks

dominicm12:11:09

If I have a unpopular library that introduces a with- macro, can I annotate it somehow so that kondo users don't need to add it to their lint configuration? Maybe something picked up as part of the full analysis

borkdude12:11:21

@dominicm I have been thinking about this as part of these issues: https://github.com/borkdude/clj-kondo/issues/253 https://github.com/borkdude/clj-kondo/issues/559 For #559 I've come to the conclusion for now that it would be most flexible to add a README page for third party library configs where library maintainers can PR their configs. https://github.com/borkdude/clj-kondo/issues/559#issuecomment-551949256 But #253 could help automate this and use rewrite-clj(c) (proper, not my fork) to include it in the config.edn

borkdude12:11:55

Also, you can include the kondo config in the README of your lib

sogaiu14:11:54

is there already support for more than one config to be merged? sort of like how for deps, ~/.clojure/deps.edn "merges" w/ a project's deps.edn

sogaiu15:11:52

i guess 5 under design principles suggests that there is no at-run-time merging. may be the external tool being considered could do this kind of thing?

borkdude15:11:39

@sogaiu Currently there is .clj-kondo/config.edn and the --config argument that are merged

borkdude15:11:46

and the ns-local config via metadata

borkdude15:11:54

and also the built-in config

borkdude15:11:59

it's by design that no multiple configs are merged from multiple .clj-kondo directories, so people store a complete configuration in a project

sogaiu16:11:02

supposing that library authors provide a config with their library, is it expected for users to have to manually merge this with their local configuration (for which the 3rd party library is a dependency)?

borkdude16:11:29

the idea of the helper tool is that it can do that for you using rewrite-clj(c)

sogaiu16:11:29

ah, so a user won't have to manually piece together 2 (or more?) existing config files?

borkdude16:11:16

the reason I want it to be another tool is that it can have more dependencies and also work in CLJS, so it can be hooked up with editor tooling

borkdude16:11:27

I'm not entirely sure about this all

borkdude16:11:02

why is there no icon for :hammock:

sogaiu16:11:10

yes, exactly

borkdude16:11:19

@lee, we need your help ^

1
lread16:11:45

ha! just a parenthesis on its back, no?

🙂 1
Filipe Silva19:11:21

is there a super obvious configuration item to lint devcards?

Filipe Silva20:11:27

I imagine the devcards macros probably have the same shape as something else and that I could use :lint-as, but I don't know what other thing is...

borkdude20:11:40

probably clojure.core/def?

Filipe Silva20:11:02

maybe, I'll try that for now

Filipe Silva20:11:23

if I use the vscode extension, I should still put the config in .clj-kondo/config.edn right?

Filipe Silva20:11:30

I notice cache doesn't seem to be there

borkdude20:11:29

does your .clj-kondo/config.edn live in the root of your opened folder?

borkdude20:11:43

the cache is only populated when you have a .clj-kondo directory

Filipe Silva20:11:01

ah yes, I didn't have it before

Filipe Silva20:11:07

so now that I made it, it shows up there