This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-10
Channels
- # ai (2)
- # beginners (3)
- # boot (113)
- # bristol-clojurians (2)
- # cider (77)
- # clara (43)
- # cljs-dev (48)
- # cljsrn (9)
- # clojure (319)
- # clojure-austin (2)
- # clojure-czech (4)
- # clojure-denmark (4)
- # clojure-france (4)
- # clojure-italy (4)
- # clojure-russia (2)
- # clojure-serbia (10)
- # clojure-spec (79)
- # clojure-uk (64)
- # clojurescript (109)
- # clr (3)
- # conf-proposals (21)
- # core-async (19)
- # cursive (26)
- # datascript (11)
- # datomic (19)
- # devcards (1)
- # emacs (25)
- # figwheel (9)
- # hoplon (31)
- # jobs (7)
- # jobs-discuss (14)
- # leiningen (10)
- # lumo (11)
- # off-topic (37)
- # om (40)
- # onyx (4)
- # perun (8)
- # planck (3)
- # rdf (4)
- # re-frame (40)
- # ring (11)
- # ring-swagger (2)
- # rum (21)
- # spacemacs (2)
- # specter (50)
- # untangled (93)
- # yada (13)
@thomas: I believe there’s a “prep-task” or something like that that allows you to add your JS compile to your build. The uberjar might run a clean, so if your JS compilation isn’t included in your build, it might get wiped.
@sineer: If you’re still having that error, the cause might be because you’ve put something like (:require ‘clojure.pprint)
instead of (:require clojure.pprint)
.
@thomas: Ah good 🙂. :prep-tasks [[”cljsbuild” “once”] “javac” “compile”]
might also work, so you add your CLJS building to your build.
@weavejester that looks very useful indeed. I might add that
@thomas I generally have that, but in my :repl
profile I turn it off with :profiles {:repl {:prep-tasks ^:replace [”javac” “compile”]}}
because I’m typically using Figwheel during REPL development.
are there any helpers in creating async-ring handlers & mw out of sync-ring counterparts? Should there be?
with sync, you return something of throw, a wrapper with try woudn't cause a perf impact.
@ikitommi You can convert a sync handler into an async handler fairly easily:
(fn [handler]
(fn [request respond raise]
(respond (handler request))))
You can’t really do the same with middleware without resorting to blocking, so a sync middleware would negate the advantages of an async handler.
Essentially everything under a sync handler is synchronous, so it’s a one-way conversion.