This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-25
Channels
- # 100-days-of-code (3)
- # beginners (80)
- # cider (53)
- # cljdoc (9)
- # cljs-dev (66)
- # cljsrn (6)
- # clojure (108)
- # clojure-austin (5)
- # clojure-dusseldorf (1)
- # clojure-italy (9)
- # clojure-losangeles (2)
- # clojure-nl (4)
- # clojure-spec (40)
- # clojure-uk (46)
- # clojurescript (60)
- # cursive (119)
- # datomic (28)
- # emacs (10)
- # events (1)
- # figwheel-main (21)
- # fulcro (16)
- # hyperfiddle (10)
- # immutant (2)
- # leiningen (1)
- # liberator (5)
- # nyc (1)
- # off-topic (36)
- # onyx (4)
- # pedestal (52)
- # portkey (5)
- # re-frame (11)
- # reagent (11)
- # shadow-cljs (46)
- # sql (1)
- # unrepl (2)
Hello friends, does any one has built an open-source fulcro project with an old plain RESThellAPI. I’d like to see pathom in action with fulcro to compare with plain parser dev.
@U2N9GDB1U Don't know about open-source rest with pathon but there is a fulcro video that shows off pathom https://youtu.be/gbrdnSsUerI?t=16m6s
Thanks a lot
@tony.kay i know you try not to make breaking changes to fulcro’s public API, does that include fulcro.client.network
?
i need to make some xhr requests in a way that libraries like cljs-ajax
and cljs-http
are not able to handle
i could use goog.net.XhrIo
, but it seems like you already have a nice cljs friendly wrapper for it
also, i’m only using it for CORS requests, nothing on the server
the new remotes support middleware on the client, which lets you completely morph the request and response.
ah cool
also, i was reading the closure docs and they seem to suggest that it’s inefficient to create a new xhrio instance for every request https://developers.google.com/closure/library/docs/xhrio
which is what the static method does
and it seems like we’re doing that in fulcro too, despite using the instance method
i haven’t noticed it to be a bottleneck, but would you care for a PR that re-uses the xhrio instance?
then again we probably shouldn’t prematurely optimize…
you were right, using the middleware was easy