This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-01
Channels
- # adventofcode (30)
- # announcements (51)
- # aws (27)
- # babashka (1)
- # beginners (16)
- # calva (6)
- # cider (10)
- # clj-kondo (2)
- # clojure (94)
- # clojure-dev (27)
- # clojure-italy (1)
- # clojure-taiwan (1)
- # clojure-uk (5)
- # clojurescript (18)
- # clojutre (2)
- # cursive (14)
- # data-science (8)
- # emacs (2)
- # joker (5)
- # off-topic (3)
- # shadow-cljs (31)
- # sql (2)
- # vim (2)
- # yada (11)
@robert-stuttaford There’s nothing built-in in CIDER to do this, but you can easily override the printing function.
Is cider-inspector suppose to work in clojurescript? I'm trying to inspect a very simple data {:a 1}
, but it fails.
thanks @bozhidar - i ended up monitoring the repl buffer and crafting what i need with println + pprint
Is there a general approach to work with dependency injection (Component, mount, integrant...) in CIDER?
Usually I use M-.
to jump to the source of a function. However with dependency injection all I have is a keyword extracting a function from a map at runtime 😕
not really. that's part of dependency injection that is frustrating: dependencies are runtime configurations
Frustrating indeed. Thanks, at least I know I'm not just being bad 😛
Perhaps there's something to be done with a mix of enlighten and jump to source. For example once we run it, it could show temporary vars that can be used to jump to namespaces.