Fork me on GitHub
#cider
<
2019-12-01
>
bozhidar15:12:58

@robert-stuttaford There’s nothing built-in in CIDER to do this, but you can easily override the printing function.

tianshu15:12:51

Is cider-inspector suppose to work in clojurescript? I'm trying to inspect a very simple data {:a 1}, but it fails.

robert-stuttaford16:12:46

thanks @bozhidar - i ended up monitoring the repl buffer and crafting what i need with println + pprint

frozenlock22:12:54

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 😕

dominicm08:12:23

I wrote juxt/clip to address this problem, in part.

dominicm08:12:47

It uses symbols instead of keywords, and those symbols correspond to vars

👍 1
dpsutton22:12:25

not really. that's part of dependency injection that is frustrating: dependencies are runtime configurations

frozenlock22:12:43

Frustrating indeed. Thanks, at least I know I'm not just being bad 😛

frozenlock22:12:14

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.

dpsutton22:12:27

i don't follow. but taking component to be concrete, you'd want to jump to the source of a function parameter. that sounds tough