This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-26
Channels
- # aleph (1)
- # announcements (9)
- # aws (6)
- # babashka (18)
- # babashka-sci-dev (25)
- # beginners (79)
- # calva (30)
- # cider (34)
- # clj-kondo (25)
- # cljsrn (6)
- # clojure (26)
- # clojure-australia (1)
- # clojure-europe (6)
- # clojure-norway (1)
- # clojure-poland (6)
- # clojure-uk (3)
- # clojured (2)
- # clojurescript (14)
- # datomic (19)
- # events (1)
- # google-cloud (1)
- # gratitude (2)
- # helix (1)
- # hyperfiddle (2)
- # interceptors (1)
- # jobs (17)
- # joyride (96)
- # leiningen (5)
- # lsp (20)
- # minecraft (2)
- # nbb (5)
- # other-languages (1)
- # re-frame (34)
- # releases (2)
- # shadow-cljs (15)
- # spacemacs (1)
- # xtdb (19)
Hum, I can take a look soon, but it may be related with deftype be a protocol-impl and not a var-def, but we probably can fix on LSP side
Would it make sense to add a refactoring for namespaced map <-> map without default namespace (not sure if there is a name to distinguish this)? Like #:foo{:bar 1}
<-> {:foo/bar 1}
?
@UKFSJSM38 Thanks, will do. I haven't done a dive to figure out how to contribute such features yet. Is posting issues like this helpful to the project? Want to make sure I'm not creating unnecessary noise 🙂
We can discuss the impl details and what the feature would be in the end there as well
Renaming namespaces is awesome! Renames/moves the source file, updates references. That was you right, lsp? Thanks!
maybe bug report, maybe configuration issue with my set up: when I trigger signature help, it doesn't update the position of the current parameter (or active signature) when I'm between parameters: (filter even? |)
acts as if I'm still inputting the predicate
if I put in another character, it selects the next signature and the next parameter, but I would expect/like it to select those when I've input a space, as that's categorically moving on from the previous signature
yeah, it's a "expected" behavior on clojure-lsp side, the issue is: we parse the code with rewrite-clj and we would need to know when to know user is trying to add a new arg
not sure we could assume a space + cursor on that position should show a next arg, maybe yes
cool, as long as it's expected behavior I won't sweat it too much. I'd prefer it to assume I'm on the next arg but that's pretty small