This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-15
Channels
- # announcements (2)
- # babashka (41)
- # beginners (10)
- # calva (62)
- # chlorine-clover (70)
- # cider (19)
- # clara (2)
- # clj-http (1)
- # clj-kondo (1)
- # cljs-dev (3)
- # cljsrn (8)
- # clojure (168)
- # clojure-austin (1)
- # clojure-australia (2)
- # clojure-canada (1)
- # clojure-europe (15)
- # clojure-france (9)
- # clojure-nl (3)
- # clojure-serbia (5)
- # clojure-spec (14)
- # clojure-uk (8)
- # clojurescript (14)
- # community-development (30)
- # core-async (42)
- # core-typed (1)
- # datahike (2)
- # datalog (23)
- # datomic (4)
- # emacs (4)
- # figwheel-main (4)
- # fulcro (60)
- # ghostwheel (4)
- # girouette (1)
- # gorilla (7)
- # graalvm (11)
- # heroku (8)
- # integrant (42)
- # jobs (6)
- # jobs-discuss (47)
- # kaocha (7)
- # lambdaisland (2)
- # leiningen (5)
- # lsp (29)
- # off-topic (1)
- # pathom (9)
- # portal (6)
- # re-frame (5)
- # reagent (11)
- # releases (6)
- # remote-jobs (10)
- # shadow-cljs (112)
- # testing (55)
- # vrac (1)
Does anybody experience the same wrong warning from clj-kondo?
(defn ^:export init! <-- unused init! public fn
[]
(mount!))
Ahh. Sorry @U04V15CAJ. You're right. I thought that clojure-lsp relies on clj-kondo entirely when it comes to code checking! Thanks!
Is this the right default behavior? It seems common for (non-private) functions to be unused within a namespace.
yes, it's the default behaviour, there are corner cases like API public functions and datomic functions I think but user can disable for some namespaces like in the docs
Found another bug in clojure-lsp. When moving the cursor to (:require) line, the namespace line vanishes.
Thank you @UKFSJSM38
Hmm, I'm getting a lot of failed tests in the master
branch
Hmm, I'm not sure how to answer that.
I run clojure -M:test/runner
where
:test/runner
{:extra-paths ["test"]
:extra-deps {eftest/eftest {:mvn/version "0.5.9"}}
:main-opts ["-e" "(require,'[eftest.runner,:refer,[find-tests,run-tests]]),(run-tests,(find-tests,\"test\"))"]}
Interesting, yea it's all fine with make test
Do you know how
:test/runner
{:extra-paths ["test"]
:extra-deps {eftest/eftest {:mvn/version "0.5.9"}}
:main-opts ["-e" "(require,'[eftest.runner,:refer,[find-tests,run-tests]]),(run-tests,(find-tests,\"test\"))"]}
is different? (I just stole this alias off https://app.slack.com/team/U05254DQM's config)@UR37CBF8D It's probably the -e
option in the :main-opts
as that approach is a bit of a hack. I will check to see if there is a better way to make an alias for eftest.
I do prefer using lambdaisland koacha as a test runner (or cognitect labs runner)
Or it could be eftest running unit tests in parallel when the tests aren't happy being run in parallel, especially if make test
doesn't use eftest
Right. Thanks @U05254DQM I'll try out kaocha
Ah yes, the Makefile simply calls clojure -M:test
which is an alias that runs kaocha via Clojure.main
So you can also run clojure -M:test
directly or if using my user level aliases, clojure -M:test/runner
Thanks @U05254DQM. I changed kaocha to eftest because it felt faster. I'll give koacha another try
@UR37CBF8D
Running eftest using the :multithred? false setting does run the clojure-lsp tests successfully, so it does seem that the lsp unit tests should be run in in sequence, rather than the default parallel mode that eftest uses.
I added a :test/eftest-sequential
alias to practicalli/clojure-deps-edn that works with clojure-lsp test
Ahhh, I see. That makes sense
I'm on this commit:
commit 8a294181096a151cd4ee845a127b6e7306805800 (HEAD -> master, upstream/master)
Author: Eric Dallo <[email protected]>
Date: Tue Apr 13 22:02:27 2021 -0300
Improve resolve-macro-as command to check and log if couldn't resolve the macro.