This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-07
Channels
- # 100-days-of-code (1)
- # announcements (10)
- # aws (2)
- # beginners (134)
- # calva (25)
- # cider (29)
- # cljs-dev (43)
- # clojure (130)
- # clojure-dusseldorf (3)
- # clojure-italy (27)
- # clojure-nl (48)
- # clojure-spec (32)
- # clojure-uk (63)
- # clojurescript (75)
- # core-logic (5)
- # cursive (18)
- # datascript (2)
- # datomic (37)
- # emacs (5)
- # figwheel (13)
- # figwheel-main (55)
- # graphql (1)
- # java (7)
- # jobs (11)
- # jobs-discuss (19)
- # juxt (1)
- # leiningen (16)
- # luminus (10)
- # mount (3)
- # off-topic (40)
- # om (1)
- # onyx (1)
- # pedestal (7)
- # re-frame (40)
- # reagent (81)
- # ring (2)
- # shadow-cljs (32)
- # spacemacs (5)
- # testing (1)
- # tools-deps (48)
Is there a way to convert a deeply nested form like:
(clojure.walk/keywordize-keys (json/parse-string (:body (client/get "myurl"))))
into a threading macro variant?
loving the new deps.edn support. just one annoyance, the REPL output window that pops up when starting a run config. Can that popup be disabled? I don’t see any use for it
@cfleming I'm going to be "that guy" and make a bug report with a very limited amount of data. At work my REPLs only ever print one exception. I can submit forms and get results, but if there's any sort of error (compiler or runtime) I get a stacktrace for the first error, and after that, nothing. It doesn't hang the REPL, I simply get no response.
Same effect if the exception happens via run-tests
command sent with a keybinding, loading a file, etc.
So I can get sessions like this:
Loading foo.bar....
=>(+ 1 2)
3
=>(run-tests)
Running tests....
=> (/ 1 0)
=> (let [foo/bar 34] x)
=> (+ 1 2)
3
The "...." lines being lines where we start to load a file, run a test, and then nothing.
This is what I see
Yeah so it applies to local linked transitive dependencies. Sometimes only though .. I had a project where it worked fine :thinking_face:
in my case above it is a monorepo - data point
That’s just coming back from deps - I’ve seen that error on the command line sometimes too.
I don’t know why it’s required sometimes and not others - might be a question for #tools-deps.
The workaround is to specify :deps/manifest :deps
in the dependency alongside the `:local/root’
Oh ok got it I had never seen that, thank you Colin!
Trying to implement a class using gen-class
and use it in the REPL. Project is using deps.edn. What is the correct workflow in cursive? Currently getting IncompatibleClassChangeError
when trying to import.