This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-21
Channels
- # aleph (7)
- # beginners (79)
- # calva (1)
- # cider (5)
- # clj-kondo (12)
- # clojure (7)
- # clojure-austin (1)
- # clojure-brasil (2)
- # clojure-chicago (1)
- # clojure-europe (2)
- # clojure-seattle (4)
- # clojurescript (68)
- # data-science (1)
- # datavis (1)
- # figwheel-main (2)
- # hoplon (2)
- # juxt (1)
- # leiningen (3)
- # luminus (8)
- # off-topic (65)
- # onyx (1)
- # pathom (12)
- # reagent (6)
- # reitit (3)
- # shadow-cljs (7)
- # spacemacs (5)
Hi, Why in this minimal case when the :status is 500 wrap-request throws an Exception java.lang.String cannot be cast to manifold.stream.core.IEventSource. Otherwise if I change the status to 200 the unhandled exception does not occur anymore.
@U0516053R btw, is it ok to wrap your server handler in a client middleware?
I'm assuming that it is. The checking that I did was , http/post's middleware defaults do identity (so no middleware at the client by default). I assumed that it was like ring (plug middleware at server). But I didnt relate the word client with with that fact that It had to be used at client.
@dimovich Thnx for pointing the rookie mystake. Very much appreciated.
@dimovich looks good to me. If the mw also can return deferred, you need to convert 'em too.
In general, the interceptor pattern fits much better with async: the interceptor executor takes care of passing the unwrapped maps to step functions. Just need a de facto specification to interceptors, to get an ecosystem of interceptor libs, like there is for ring. #interceptors btw.