Fork me on GitHub

hello @mail228, welcome, most of what you need should be present in the pathom documentation, did you give it a try? for the parser, there is not a lot special about the storages you mentioned, if you use local storage its simpler because its sync, but pathom also supports async so its also fine if you wanna use indexeddb or something like it


@wilkerlucio Thanks, I skimmed the Connect chapter (3) and I think I got the parser up and running. I could make queries and have them resolve correctly. The problem I can't figure is how to keep Pathom resolvers and parser local and have Fulcro use that for querying. The template generates a server (which makes sense for most cases), but I haven't been able to it just client-side


Thanks, this seems to use a server for storing data, right? I need to just have everything on the client, in theory only have .cljs files in the project, since there is no /api endpoint to call


@mail228 I'm lacking a proper example for simple setup, but you can piggieback on this one:


this is a graphql connect setup on client only, just remove the graphql parts and it should work, please let me know if that is enough to get a setup

Björn Ebbinghaus12:04:45

@mail228 As I understand pathom, this ist fairly simple. You could nearly use my serversite code... and create a pathom-remote for fulcro (the functions prefixed with dbas/ are actually returning core.async channels) and


Thanks @wilkerlucio I will try it out when I get back from work 🙂


@U4VT24ZM3 Interesting, what does :dbas mean? I don't see it mentioned in the Pathom guide

Björn Ebbinghaus12:04:22

It is my own namespace. Has nothing to do with pathom


Ah, is that a replacement for remote? I see you use (dbas in defmutation


just like bjorn did as well, you create a pathom parser and use it as a fulcro remote


So to understand, the name I give here in this case :dbas is then available as (dbas in defmutation?


Then Fulcro understands this is possible to query and gets its data from that?

Björn Ebbinghaus12:04:45

:dbas is the name of the remote, yes

Björn Ebbinghaus12:04:38 Here is the only place I use the dbas remote nowadays. (I don't use the remote, because I had to ditch a feature)


Okay, I think it's clicking now!


I start to see how it works


Thanks so much both, I look forward to try later when I get home 🙂


you can also just use as a default remote, this way you don't have to specificy the remote name on the load calls


I usually give custom names only for extensions (when its something not related to the main app, or some special kinds of remotes like ones targetted for uploads, etc...)


How do I specify a default remote?


in the code example I sent to you on graphql there is the full setup, basically just set as :networking (pathom-remote ...) or :networking {:remote (pathom-remote ...)}


on the fulcro side


Ah so :remote is the default name?

Björn Ebbinghaus12:04:42

Yes, from the docs

`:networking` (optional). An instance of FulcroNetwork that will act as the default remote (named :remote). If
  you want to support multiple remotes, then this should be a map whose keys are the keyword names of the remotes
  and whose values are FulcroNetwork instances.


@U4VT24ZM3 How did you find that :thinking_face: I went here clicked cljdoc, end up here but I see no API docs. It does work on 2.8.0 though

Björn Ebbinghaus12:04:13

It is in the docstring of the make-fulcro-client funktion.


Ah makes sense, didn't think of checking source code, thanks 🙂 I'll notify in #fulcro that namespaces docs are missing


Looks like it works, I can at least query from Fulcro Inspect, thanks for your patience @U4VT24ZM3 @wilkerlucio

Björn Ebbinghaus15:04:18

Don't forget to make use of the autocompletion feature. Click the grey circle in the top right corner of the query screen. I found it way too late.

✔️ 8

ohhh that's what it do lol I clicked it before I got it working and didn't understand


if you change the index (add resolvers/mutations) remember to click again on the ball to refresh it


what is the state of the non-parallel parser? I'm trying to use it but somehow it works differently than the parallel one although I'm not doing anything async


the example doesn't in the readme doesn't seem to work for example


@thheller using the non-parallel parser requires you to use different readers


I suggest pc/reader2 instead of pc/parallel-reader, also need to use the regular mutate


@thheller try checking the example code right above this anchor, that should be a regular sync functional setup, please let me know if you find issues with it


ah I just commented out the parallel-reader


but that's the reader that does all the connect things, you may need it 🙂


but use reader2 instead for the sync parser


ok thx, that works


in which part of the doc you tried to look for this information? so I may add it there, or a link or something


all the examples used the parallel-parser so I thought the sync parser was maybe deprecated or so