This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-23
Channels
- # announcements (3)
- # aws (2)
- # babashka (31)
- # beginners (14)
- # calva (14)
- # cider (4)
- # clj-kondo (1)
- # clojure (24)
- # clojure-europe (18)
- # clojure-gamedev (4)
- # clojure-nl (3)
- # clojure-norway (23)
- # clojurescript (24)
- # core-typed (23)
- # data-science (9)
- # datomic (1)
- # emacs (15)
- # events (4)
- # gratitude (3)
- # introduce-yourself (1)
- # leiningen (9)
- # lsp (65)
- # membrane (39)
- # music (1)
- # nbb (1)
- # obb (8)
- # reitit (17)
- # releases (1)
- # tree-sitter (2)
- # vim (28)
- # xtdb (3)
This is for :aliased-namespace-symbol
https://github.com/clj-kondo/clj-kondo/blob/master/doc/linters.md#aliased-namespace-symbol
Hum, I see, is this linter new? Also what are the code actions available on that line?
I see, that could be a code action or part of clean-ns, not sure if would be good touch the rest of the code on clean-ns, but a code action to fix that line is convenient indeed
I will only enable linters that can detect serious problems or where the compiler may also warn, from now on
Love this action
@UJY23QLS1 Also check out :config-in-comment
in which you can tweak linters for RFCs
https://github.com/clj-kondo/clj-kondo/blob/master/doc/config.md#override-config-in-comment-forms
That's super cool! Along with the other :config-in-*
keys. While my usages of the above action isn't as global, I'm very happy to learn about those.
Crossposting from #emacs - maybe someone knows the answer here (I couldn't find anything via Google searches) https://clojurians.slack.com/archives/C099W16KZ/p1666466293640729
I'm on
clojure-lsp 2022.06.22-14.09.50
clj-kondo 2022.06.22
and yeah - other code actions are indeed availableso odd - it works in other projects but not in the one I've been working on so far, I'll dig into it
I think I found it - the require option doesn't show up until I open the file with that namespace in other buffer, until then Emacs is not aware if that namespace exists so it only suggests creating it
It's weird because at least lsp-mode handles and shows a message that server sent when the classpath fails
Same thing after upgrading - I have to open a buffer in emacs for the 'add require' option to show up and work, very weird.
Ok, found the reason - Eglot uses project.el
under wraps, and that sometimes fails to detect correct project root (I work in a mono repo)
It feels faster than clojure-lsp for sure, sometimes things don't work exactly the same but it might be due to how some of my projects are setup
I'd like to add functionality to my vim setup (with Conjure) that replaces the bindings in a let
-block with a sequence of def
s. Would clojure-lsp be the place to add that? Alternatively I can build on Conjure's useful tools.
It's serviceable for one-offs, but quite tedious in big let
s.
But that was actually just an example for the broader question: is clojure-lsp the place to add that type of functionality?
I see, so for common refactors we could code a code action for that, but if your question is: Can I code my own refactorings, the answer ATM is no
But of course, one could also do their own thing with a babashka script and rewrite-clj
Also looking to use/create something to load a stacktrace's locations into the vim location list
I cretaed this issue to discuss and think more about this possible feature: https://github.com/clojure-lsp/clojure-lsp/issues/1333