Thanks @U08E8UGF7 for the pointer here 1. I guess that here’s the relevant doc https://wilkerlucio.github.io/pathom/v2/pathom/2.2.0/core/mutations.html And https://wilkerlucio.github.io/pathom/v2/pathom/2.2.0/connect/connect-mutations.html Do you know of any other example of pushing data to a non-clojure server? 2. Got it 👍

1. yes, those are the correct docs what do you mean by pushing to non-clojure servers? In the context of Pathom that does not make sense to me

Hmm, I was thinking about using Fulcro+Pathom with a firebase backend

Oh, in that case I would write a CLJS pathom remote for Fulcro and fire off Firebase calls in the mutation resolvers

I thouhgt you were planning to use Pathom for the backend

Na, not yet - I’m inclined towards the pure frontend use cases.

Then these firebase calls would need to be written against the REST interface right? https://firebase.google.com/docs/projects/api/reference/rest

probably, this is new territory for me as well

Mm got it, your pointers have been a good help man!

@U2BU9G0LT to help thinking about it, consider that Fulcro only communicates using EQL, so any communication has to go via it, this means keywords for requesting data and mutations to change the world (in any way, like sending messages to firebase operations), makes sense?

Hi @U066U8JQJ, basically Pathom is the communication layer for Fulcro wrt outside world right, I get this. I guess to integrate with any rest/graphql backend it's important to teach this layer how to interpret the servers format right?

yeah, correct, I prefer to say EQL because Pathom is an impl of it, but you can make your own if you want, that is no direct thing connecting fulcro and pathom, instead both talk EQL

I think the distinction is important, because the language is formal and helps to understand the boundaries

Cool, will remember this :) Thanks!