This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-17
Channels
- # announcements (1)
- # babashka (94)
- # beginners (76)
- # calva (24)
- # cider (24)
- # clj-kondo (1)
- # cljs-dev (16)
- # cljsrn (45)
- # clojure (135)
- # clojure-europe (9)
- # clojure-france (5)
- # clojure-germany (2)
- # clojure-italy (12)
- # clojure-losangeles (13)
- # clojure-nl (3)
- # clojure-portugal (54)
- # clojure-uk (20)
- # clojurescript (55)
- # conjure (67)
- # core-async (5)
- # cursive (2)
- # datomic (10)
- # docker (7)
- # duct (22)
- # emacs (16)
- # fulcro (34)
- # graalvm (15)
- # hoplon (1)
- # instaparse (1)
- # jobs-discuss (3)
- # juxt (94)
- # luminus (1)
- # meander (4)
- # off-topic (13)
- # pathom (4)
- # pedestal (1)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (61)
- # spacemacs (17)
- # specter (2)
- # sql (23)
- # xtdb (33)
There's some weird stuff here though. If I evaluate a namespace form I get three responses.
I hope I haven't discovered race conditions etc 😭 it's receiving my code with one id and sending the result back on another id.
Also it's mangling file path metadata so I can't go to def. I'll timebox and try to work around some of this then move back onto features.
Added a workaround config so you can prefix all paths for go-to-def. Although there's no real way to know that you have to set it and what to set it to.
Found a much better way! Go to def now uses :find
which means you get a nice error if it tried to open a file and failed. Then you can just set your Vim path to contain the right source directories.
No worries, I'm going to describe
on connect and then use that to check available features.
Sorry, bad word really, I mean that the absoluteness of the path was being lost and became relative to the path of the JVM / CLJS?
Which isn't so bad on it's own really, just made it harder to know how to find that file in the project.
But since you can add to your vim path, that's a nice way to handle it I think so no big deal really!
Yep, no biggie really. In CLJ land it took my absolute path and ran with it, but that won't always be the case and that's okay.
you get multiple because it does multiple async commands and just tells you too much about what it is doing
Would it be bad if I leaned on CIDER even for things like documentation lookup :thinking_face:
It'll make it so much easier to provide a good experience, right now I'm taking the easiest hackiest approach to some features. CIDER polishes them and makes them easy to hook into.
i feel like that approach makes a lot of sense. standing on the shoulders of giants and whatnot
Yeah, I'm basically checking for individual ops so if some things are missing that's okay. Maybe I'll have a fallback doc system, it'll just be annoying maintaining two, it's a bug risk imo
Not sure if I should be using eldoc for rendering my own doc output 😬 should probably be using info I guess. But I like the parsed arg lists.
Also noticed if I did it on add
before I defined my add
function it returned a list of candidates. So then I log out the possible candidates classes that contain the add
method and you can hit K
on the one you're interested in.
I'm going to add a couple of commands for figwheel-main and shadow-cljs support out of the box too.