Fork me on GitHub

I've started trying to implement something where I have attributes refer to a particular websocket connection which has a resolver which initializes the websocket as well as a core.async/mult ("assigned" to another attribute). Then I assign other "Stream types" to an attribute and give them a resolver which both send a message to the websocket to start receiving messages (if that stream type hasn't been created yet) and tap the mult, and wrap the new channel in another mult. In this way I could have a graph of core.async mults that mirrors the pathom graph, and I just query for these mults and tap them in my app. I imagine I will have to manage my own cache with this approach. Are there other obvious reasons this is a bad idea? Has anyone used Pathom to manage stateful components like this?

Alexander Kaiser12:04:42

Pathom with GraphQl and fulcro 3 Hi, first of all, thank you very much for that fantastic library! I am absolutely fascinated by it. Is there currently an recommended way to use fulcro 3 with pathom and a graphql data source? (preferably via a graphql remote). - The ways mentioned in the pathom 2 tutorial are only supported by fulcro 2 and it seems to be a bit more complicated to port them to fulcro 3 ( has some dependencies that don't seem to exist anymore in fulcro 3) - pathom 3 looks absolutely awesome but has no graphql helper at the moment I am new to pathom and fulcro. Sorry if I am missing something obvious.


Here's an example project that integrates fulcro 3 with a graphql API via pathom 2:

👍 3
Alexander Kaiser21:04:10

Thank you very much, this helps a lot.

👍 3

@alexander.kaiser I would recommend asking in #fulcro, as it sound more topical and people there may be able to help you with the fulcro integration better

👍 3
Alexander Kaiser21:04:47

Thanks for pointing this out. I will post future questions regarding this in fulcro channel.