This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-17
Channels
- # announcements (17)
- # aws (2)
- # babashka (21)
- # beginners (67)
- # calva (19)
- # cider (29)
- # clara (3)
- # clj-kondo (6)
- # cljsrn (10)
- # clojure (140)
- # clojure-europe (164)
- # clojure-nl (3)
- # clojure-uk (8)
- # clojurescript (62)
- # conjure (7)
- # core-async (24)
- # cursive (21)
- # datomic (5)
- # docker (40)
- # emacs (14)
- # fulcro (25)
- # gratitude (1)
- # honeysql (6)
- # introduce-yourself (1)
- # jobs (1)
- # jobs-discuss (32)
- # juxt (7)
- # lsp (13)
- # minecraft (2)
- # off-topic (49)
- # pathom (24)
- # practicalli (8)
- # re-frame (18)
- # react (23)
- # remote-jobs (6)
- # reveal (2)
- # shadow-cljs (75)
- # tools-deps (7)
Hi all, I appear to be having some classpath issues using calva/clojure-lsp and a new fulcro project. Does anyone have any experience with fixing classpath issues for deps.edn + shadow-cljs full-stack projects like this (mix of cljs/cljc/clj)?
Hmm, so doing that, the classpaths look normal for both outputs of clojure -Spath
and npx shadow-cljs classpath
. There are no errors thrown by the lsp.
so what made you think that calva/clojure-lsp was having issues with the classpath?
oh right, that is not related with the classpath scan, but with false-positives/clj-kondo configuration indeed :)
Take a look at this: https://github.com/clj-kondo/clj-kondo/blob/master/doc/config.md#unrecognized-macros
I can dig around in the fulcro config from https://github.com/clj-kondo/config
@U1EPFAJ1J probably a lot of problems will be solved if you try to add this to your clj-kondo config:
:configs-paths ["com.fulcrologic/fulcro"]
ref: https://github.com/fulcrologic/fulcro/tree/develop/src/clj-kondo/clj-kondo.exports/com.fulcrologic/fulcromaybe it should help with different issues like repl or static analysis or just route to the slack for ask questions
Yeah, this might save us some back-and-forth conversation with regards to asking people for more information/clarification.
It also risks raising a barrier. I generally think that the issues posted are good and actionable. Also enjoy the conversations more than I think they are a bother. That said, we can probably populate the templates in a way that doesn't feel so much like hitting a brick wall. And encouraging using this channel to investigate a bit is a nice idea!