This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-19
Channels
- # announcements (24)
- # asami (25)
- # babashka (17)
- # beginners (99)
- # bitcoin (1)
- # calva (2)
- # cider (6)
- # cljs-dev (4)
- # clojure (88)
- # clojure-australia (3)
- # clojure-europe (23)
- # clojure-france (6)
- # clojure-nl (5)
- # clojure-uk (31)
- # clojured (1)
- # clojurescript (6)
- # clojureverse-ops (1)
- # datomic (28)
- # depstar (18)
- # emacs (11)
- # events (1)
- # fulcro (21)
- # graalvm (4)
- # graphql (7)
- # heroku (1)
- # jackdaw (18)
- # joker (3)
- # kaocha (1)
- # lsp (1)
- # malli (13)
- # meander (4)
- # off-topic (12)
- # pathom (14)
- # pedestal (2)
- # podcasts-discuss (1)
- # re-frame (37)
- # reagent (17)
- # reitit (9)
- # shadow-cljs (44)
- # xtdb (17)
I really like cider-clojuredocs
as someone who’s learning; however, in a cljs file one gets 'cider-clojuredocs' doesn't support ClojureScript
so I have to change the mode to clojure-mode for the buffer then it will work; however, almost all the symbols I am looking up are not specifically cljs ones… is there a way to get it to work for those symbols without having to change the buffer mode to clj and back?
I might remove this error at some point - the problem is that ClojureDocs really lists only Clojure namespaces and as some are named slightly differently (e.g. cljs.core
) I didn't want to put a translation map between them.
At this point I tend to agree it'd better to just give errors about missing symbols than some blanket error statement. Feel free to open a ticket about this. It's trivial to change it.
I see on the backend that we resolve the symbols as Clojure syms, which I assume won't work when routed via a ClojureScript REPL, and this is probably the actual reason for the error message.
Ah, ok. Sweet!
Since a lot of people are coming into Clojure via ClojureScript and the community docs are so much more helpful for people new to Clojure this’ll be awesome.