This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-11
Channels
- # announcements (1)
- # architecture (23)
- # beginners (189)
- # boot (1)
- # calva (62)
- # clj-kondo (23)
- # cljs-dev (9)
- # clojure (336)
- # clojure-dev (11)
- # clojure-europe (2)
- # clojure-italy (17)
- # clojure-nl (25)
- # clojure-uk (53)
- # clojurescript (12)
- # core-async (29)
- # data-science (1)
- # emacs (6)
- # fulcro (23)
- # garden (3)
- # graphql (2)
- # jobs (1)
- # joker (7)
- # off-topic (17)
- # om (2)
- # qlkit (1)
- # reagent (15)
- # reitit (18)
- # rewrite-clj (7)
- # shadow-cljs (176)
- # sql (1)
- # test-check (4)
- # vim (32)
- # xtdb (30)
simple example: https://www.dropbox.com/s/8hwjal4aihae4gu/Screenshot%202019-06-11%2017.44.32.png?dl=0
@thenonameguy would you like to run with a binary (if so, linux or mac), or the clojure version (JVM)?
that would be fine, but here’s the MacOS binary just in case: https://3562-176829714-gh.circle-artifacts.com/0/release/clj-kondo-2019.06.08-alpha-SNAPSHOT-macos-amd64.zip
the branch with the work in progress is called unresolved-symbols
in case you want to try it with clj
This is the issue, in case you want to report anything: https://github.com/borkdude/clj-kondo/issues/174
thanks, I’ll report back. It seems to work btw, I’m just seeing false positives like deftest, I’ll probably have to create a new cache for this
deftest should work, but you’ll have to use :require
(unless I’m not understanding correctly your false positive)
./test/main/atlas/s3_test.clj:8:2: error: unresolved symbol use-fixtures
./test/main/atlas/s3_test.clj:9:4: error: unresolved symbol compose-fixtures
./test/main/atlas/s3_test.clj:16:2: error: unresolved symbol deftest
(ns atlas.s3-test
(:require ...
[clojure.test :refer :all]
...))
(use-fixtures :once
...
I could make it work, technically, but it would be a lot more complex and at the same time, I think it make sense if we abandoned use and refer all as a community. Even more so, since ClojureScript doesn’t support it, so you’re already on your way to good .cljc if you adopt this practice.
but I was going to write a “how to ns” kind of linter, which is also will help you with this: https://stuartsierra.com/2016/clojure-how-to-ns.html