This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-19
Channels
- # announcements (3)
- # babashka (42)
- # beginners (84)
- # calva (3)
- # cider (13)
- # clj-kondo (9)
- # cljs-dev (6)
- # cljsrn (32)
- # clojure (47)
- # clojure-argentina (4)
- # clojure-france (2)
- # clojure-spec (17)
- # clojure-uk (15)
- # clojuredesign-podcast (4)
- # clojurescript (41)
- # conjure (53)
- # cursive (16)
- # data-science (5)
- # duct (1)
- # emacs (11)
- # events (1)
- # exercism (3)
- # fulcro (48)
- # graalvm (20)
- # graphql (1)
- # joker (3)
- # kaocha (2)
- # malli (2)
- # meander (6)
- # pathom (3)
- # planck (18)
- # rdf (3)
- # re-frame (14)
- # ring-swagger (1)
- # shadow-cljs (15)
- # specter (1)
@dpsutton There is something along those lines that was made public for use by Emacs...
Hmm. I’d love to know. I’m revamping inf-clojure and wanted something. As far as I can tell it throws warnings about being non-public
ljs.user=> (planck.repl/get-completions "map")
^
WARNING: var: planck.repl/get-completions is not public at line 1
#js ["map" "MapEntry" "map" "map-entry?" "map-indexed" "map?" "mapcat" "mapv"]
cljs.user=>
Yeah, I don't see why something like that couldn't be made public. (Or perhaps a variant that returns a vector...)
yeah i think for our purposes a simple vector would be better. but we can always handle the marshalling on our side
In the meanwhile, if you want to see how it would behave without warnings, I wonder if you can get away with calling it as (@#'planck.repl/get-completions "map")