Fork me on GitHub
#clj-kondo
<
2020-05-16
>
gerred16:05:19

I'm trying to get the right config.edn for a pedestal macro defroutes

gerred16:05:50

gives me an unsatisfying [Error - 12:03:11 PM] [email protected] error

borkdude16:05:18

@gerred

(ns foo
  {:clj-kondo/config '{:linters
                       {:unresolved-symbol
                        {:exclude [(io.pedestal.http.route.definition/defroutes)]}}}}
  (:require [io.pedestal.http.route.definition :refer [defroutes]]))

(defroutes x)

gerred16:05:42

thank you!

borkdude16:05:52

btw, I don't know this macro, but if it's similar to compojure/defroutes, you could try lint-as

borkdude16:05:03

because there is built-in support for compojure

borkdude16:05:12

but I bet it isn't

gerred16:05:34

yeah pedestal takes a different structure

vinnyataide16:05:29

@gerred still showing the unsatisfying error here

gerred17:05:00

really? it's working for me now. I did have to (declare routes) to make my var quote work

kari17:05:09

I was reading some old posts and I understood that LSP is the preferred method to configure clj-kondo with IntelliJ IDEA (and not File Watcher)?

didibus18:05:28

Clj-kondo does not work in ClojureScript correct?

didibus18:05:48

If you wanted say a browser editor to support some of its linting?

borkdude18:05:29

@kari.marttila just choose the one that works

kari19:05:48

Thanks! clj-kondo is a great tool - very popular at Metosin.

borkdude18:05:40

@didibus clj-kondo is JVM only

borkdude18:05:15

@didibus however, I made this: https://clj-kondo.michielborkent.nl/ - it's calling clj-kondo as a service

didibus18:05:37

Hum, ya I guess that can be an option. I was hoping to have a static website for this though, no server involved.

didibus18:05:54

Now just waiting for GraalVM to have a native WASM target 😋

bhaim12318:05:19

Hi Guys I'm facing an issue that maybe you already had. I have the same macro, defined in several project in different name spaces (I know it is bad, but this is the current state). (the macro is the if-let* so you can said it should be identified like the let macro). I'm trying to have one "global" config for all the projects. Not sure how to do this, was thinking about the lint-at section, but since the location of the macro in each project is different, I'm not sure it is possible. Any idea?

borkdude18:05:10

@bhaim123 you can just put multiple lint-as entries for each different namespace?

bhaim12318:05:41

@borkdude thanks for helping! I prefer not to do that since we have many different project and it will make the config really ugly 🙂

borkdude18:05:25

then use a different config for each project. I don't see anything in between those approaches