This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-07
Channels
- # announcements (12)
- # aws (2)
- # beginners (233)
- # calva (68)
- # cider (23)
- # circleci (5)
- # clj-kondo (40)
- # cljsrn (4)
- # clojars (3)
- # clojure (200)
- # clojure-austin (1)
- # clojure-canada (1)
- # clojure-dev (16)
- # clojure-europe (1)
- # clojure-finland (1)
- # clojure-italy (4)
- # clojure-nl (16)
- # clojure-spec (3)
- # clojure-uk (102)
- # clojurescript (16)
- # cursive (14)
- # datomic (16)
- # figwheel-main (7)
- # graalvm (3)
- # hoplon (37)
- # jackdaw (23)
- # jobs-discuss (24)
- # joker (4)
- # kaocha (6)
- # keechma (64)
- # off-topic (66)
- # parinfer (1)
- # pedestal (7)
- # re-frame (7)
- # reagent (10)
- # reitit (45)
- # rewrite-clj (12)
- # shadow-cljs (1)
- # slack-help (8)
- # spacemacs (55)
- # sql (9)
- # tools-deps (9)
- # vim (7)
I consider this the channel also for the Clojure style guide (because of a lack of one and because @bozhidar is here :)) So I’m going to link this here: https://github.com/borkdude/clj-kondo/issues/241 There have been discussions in several issues in different projects. I think the style guide should maybe take a stance on this
@borkdude I prefer option 2. I totally agree we should document this in the style guide. I’ve many times deleted a namespace like this, because joker told me it was unused. 🙂
What about this as an option? https://github.com/borkdude/clj-kondo/issues/241#issuecomment-500374252
[^:keep foo]
would also be possible, but some tools might not see the metadata because you can’t actually add metadata onto a symbol 😉
Well, I guess option is the most balanced then, but I assume some linters might consider an obsolete refer. 😄
about vertical alignment, it seems clojure-sort-ns already respects metadata, kind of:
(ns foo
(:require
^:keep [bar.specs]
^:keep [foo.specs]
[another.namespace.a]
[another.namespace.b]))
@borkdude Please, file a ticket on the style guide repo, so others can see/join the conversation and we’ll decide on the approach to adopt in the next few days.
Is it ok to redirect the conversation from there to the issue already open, since it already has a few comments?
Yeah, that’s fine. I just want everyone watching the repo to see we’re discussing a new rule.
noticing a weird behavior in cider cljs repls: the content of the cider-classpatch doesn't match the lein deps: tree, specifically the cider-classpath reports older version of artifacts (transitive dependency), which is causing compilation errors. any ideas?
Specifically: according to lein: [metosin/reitit "0.3.7"] [metosin/reitit-core "0.3.7"] [meta-merge "1.0.0"] according to cider-class path:
.m2/repository/meta-merge/meta-merge/0.1.1/meta-merge-0.1.1.jar