This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-25
Channels
- # aleph (2)
- # aws (2)
- # beginners (37)
- # boot (23)
- # cider (29)
- # clara (34)
- # cljs-dev (2)
- # cljsrn (17)
- # clojure (230)
- # clojure-dev (47)
- # clojure-italy (11)
- # clojure-nl (2)
- # clojure-poland (5)
- # clojure-russia (52)
- # clojure-sg (1)
- # clojure-spec (70)
- # clojure-uk (73)
- # clojurescript (31)
- # core-async (9)
- # cursive (15)
- # datomic (39)
- # events (1)
- # graphql (1)
- # lein-figwheel (2)
- # luminus (13)
- # off-topic (2)
- # onyx (29)
- # other-lisps (1)
- # parinfer (15)
- # pedestal (14)
- # re-frame (41)
- # reagent (24)
- # ring (4)
- # ring-swagger (12)
- # rum (1)
- # spacemacs (3)
- # specter (1)
- # test-check (13)
- # timbre (9)
- # unrepl (29)
- # vim (5)
I’m working on a library to format clojure.spec errors. When error are (intentionally) thrown, I see a difference between the output in *cider-repl localhost*
and in *cider-error*
- namely, *cider-error*
doesn’t look correct with respect to newlines https://gist.github.com/bhb/3a6327773c8e6b490ff249bed5c20b55
Error are thrown when spec “instrumentation” is enabled and the user calls a function with invalid params
does the *cider-error*
handle newlines in a special way or expect multi-line strings to be formatted in a specific way? I’m on cider 0.15.0
yes, can do. i have also corrected the gist: i messed it up when I tried to alter it to make the example clearer 😞
i've got to go cook some dinner but i think this is your function you want to look at:
@bbrinck can you give me a repo that has a minimum reproduction? or perhaps instructions on how to create it? I haven't delved into spec yet because it's alpha
i think it's actually cider-stacktrace-emit-indented
at issue here. i'm just not sure why the message isn't multiline, but some parts of it are
instrument the function you want to test and then C-c C-t t
to run a test at point and it should work