This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-17
Channels
- # bangalore-clj (2)
- # beginners (202)
- # boot (18)
- # cljs-dev (8)
- # cljsjs (7)
- # cljsrn (4)
- # clojars (2)
- # clojure (401)
- # clojure-boston (2)
- # clojure-dusseldorf (1)
- # clojure-gamedev (36)
- # clojure-greece (2)
- # clojure-italy (1)
- # clojure-russia (16)
- # clojure-spec (27)
- # clojure-uk (7)
- # clojurescript (68)
- # core-async (16)
- # cursive (25)
- # datascript (1)
- # datomic (34)
- # funcool (1)
- # hoplon (1)
- # interop (1)
- # klipse (1)
- # leiningen (2)
- # lumo (75)
- # off-topic (17)
- # om-next (2)
- # onyx (66)
- # re-frame (18)
- # reagent (2)
- # ring-swagger (11)
- # spacemacs (1)
- # specter (1)
- # timbre (3)
- # untangled (48)
- # yada (7)
I think I've worked out the killer clojure-spec feature for Cursive... hiding them. I find I want specs in my code because it picks up a lot of bad function calls and nil puns. Problem is that adding specs to every function is verbose and adds friction as I refactor. What I want is specs which are sprinkled on (e.g. right click a fn arg and specify a pred) and only see the spec by hovering the mouse. I'd never open the accompanying spec file.
Ya, know. Just when you have a quiet moment Colin. #loveyourwork
(equally, hiding pre/post and asserts would reduce clutter)
@olivergeorge So that’s actually pretty easy using code folding. Could you file an issue for that one and I’ll look into it? If you have a simple example of the sort of thing you’d like to hide that would be great too.
Would you like something specific to the spec side of things? I think covers the point about pre/post/asserts https://github.com/cursive-ide/cursive/issues/1406
@olivergeorge Sorry, I had forgotten about that one. If you have some simple spec examples that would be good too - do you just want s/fdef
collapsed by default?
No worries. I'll have a think about it.
Is there a way to change the stack trace repl printer? My stack traces are typically ~100 lines long, so I always need to scroll back up to the top to see the problem
@danielcompton If you have clj-stacktrace or aviso/pretty loaded in your REPL, they’ll be used.
No, but I'm using a remote REPL into a boot repl
that might have something to do with it
I thought boot automatically included aviso/pretty
I'll try put something together
@danielcompton Note that pretty has to actually be required in your app to work, i.e. the namespace has to be loaded. Is it possible boot bundles it but doesn’t load it unless you ask it to?
hmm, perhaps. I've added it myself to my deps and required it in my dev namespace and it seems to be working now
Ok, cool. I’m still interested in an example of a stacktrace that isn’t folding correctly, if you have one.
@doglooksgood No, it’s not - how would you like that to work?