This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-19
Channels
- # announcements (1)
- # beginners (115)
- # calva (7)
- # cider (8)
- # clj-kondo (3)
- # cljdoc (12)
- # clojure (50)
- # clojure-europe (4)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-spec (70)
- # clojure-uk (88)
- # clojurescript (54)
- # core-async (16)
- # cursive (5)
- # datomic (31)
- # editors (4)
- # emacs (4)
- # fulcro (29)
- # graphql (17)
- # luminus (1)
- # lumo (2)
- # off-topic (37)
- # pathom (16)
- # random (2)
- # re-frame (5)
- # reitit (3)
- # rum (2)
- # shadow-cljs (192)
- # sql (11)
Hi guys, I’ve been exploring the pathom/http/fetch
api but having problem translating the clj-http
code to the fetch
code
(-> (http/request {:method :get
:as :json
:url requestbin-url})
:body)
pathom fetch version
, I’d only like to extract the resulting :body
from this but due to async
nature only a channel gets stored in outer var
(go
(<? (fetch/request-async {::http/url requestbin-url
::http/as ::http/json
::http/method "get"})))
Suggestions are welcome 🙂@abhi18av that's the nature of async things, if you use pathom async or parallel parser you can return channels and pathom will process, async is contagious (like macros), once there you need to deal with it
Hello friends, for everyone here that asks, or try to use Pathom with Datomic, I've started working in a plugin to facilitate the integration between those two things: https://github.com/wilkerlucio/pathom-datomic
I personally don't use Pathom with Datomic myself (I'm the middle game business, calling services) so feedback is very appreciated
currently it can auto-handles queries using :db/id or unique attributes, also helpers to query for entities automatically leveraging user sub-query, full docs on README
I hope you enjoy 🙂
@wilkerlucio let me know if you need any help on that, we use them together quite a bit
thanks, for now would be great if you can try it out, and find the gaps/problems so we can iterate on it
I wish the client API supported filter
, that’s a pretty cool way to support security
@eoliphant with the plugin we can have full control, I'm still wondering about ideas to make it, the most obvious are white/black listing for some attributes, @tony.kay other day also gave the idea to have some sort of nav?
fn interface, where you get the context and decide if that attribute is allowed or not in that context (so far seems the most extensible idea)