Hello, @wilkerlucio — after listening to all your interviews with @jacek.schae, I was blown away, and watched all the videos you linked to. Congrats on continuing to build out such a remarkable and novel way managing data! After seeing the magic that’s possible, I suddenly find it quite distasteful to have to write API and database queries over and over again, and often, once on the client side, and another time on the server side! I may have been mildly annoyed about doing that before, but after seeing the SpaceX and YouTube demo that @pithyless did, I now know that it doesn’t have to be that way — and suddenly, writing the same queries in two portions of code seems intolerable! 😆 😆 😆 I’ve spent about 6 hours trying to write a resolver against the Vimeo — it’s been kind of tough sledding, because it’s taken me awhile to comprehend sufficiently how all the pieces get created. I found myself watching the “Om Next” video from @wilkerlucio several times, pausing many times to watch how he built the Spotify example. I just published my work in progress here — my goal is to document my experiences trying to write a Vimeo adapter, point out where I had sticking points, and propose some doc changes. I’ll write that up when I’m a little further down, but wanted to share progress so far, just in case it’s useful (or amusing. 🙂 I’ve written the easiest resolver (“video-by-id”), and I’m on the third attempt to get “albums-by-user-id” written — I got hung up on how to deal with the collection inside of the return value… https://github.com/realgenekim/pathom-demo/tree/gene-vimeo-hacking-away Happy to hear any critiques or recommendations on the work I’ve done so far — here’s to hoping I can get “albums-by-user-id” working in this work session tonight! Thank you, @wilkerlucio and @pithyless!

(Sorry, meant to post more, but need to run — but wanted to post something now, as opposed to more later. 🙂

Okay, for the life of me, I can’t seem to get the Vimeo equivalent to the spotify.top-tracks to work, as was shown in this repo: https://github.com/wilkerlucio/spotify-pathom/blob/master/src/spotify_pathom/parser.clj#L64 I manually assoc in a vimeo.album-list.data -> vimeo.album/user-id, creating an alias with that and vimeo.user/id. And I just can’t figure out how to write the equivalent EQL of the spotify-top-tracks. How do I get all the album URLs for a given user? Blindly copying the spotify query, I feel like it should be something like in the screenshot below from the video. Any hints much appreciated!!! 🙏🙏

hello @genekim! happy to see your excitement 🙂

@genekim not sure if I understand your question, can you send the example query you are trying to run? what you expect, and what is happening?

@wilkerlucio there is some function to remove the "cache" from env? I can do a "select-keys" and get just the index keys, but it will remove my custom env vars. Something like:

(pco/defresolver foo [env _]
  (let [... (p.eql/process (pci/without-cache env)
                           [::my-key])]
    ...))

@wilkerlucio Thx for the focusing question. My query that isn’t working looks like

[{[:vimeo.user/id 118038002]
  [* :vimeo.album-list/data
   [[:vimeo.album/uri]]]}]

{[:vimeo.user/id 118038002
  [:vimeo.album/uri "uri1"]
  [:vimeo.album/uri "uri1"]])
 

{[:vimeo.user/id 118038002]
 {:vimeo.album-list.paging/previous nil,
  :vimeo.album-list.paging/next nil,
  :vimeo.album-list.paging/last "/118038002/albums/?page=1",
  :vimeo.album-list/per-page 25,
  :vimeo.album-list.paging/first "/118038002/albums/?page=1",
  :vimeo.album-list/id 118038002,
  :vimeo.album-list/page 1,
  :vimeo.album-list/total 8,
  :vimeo.album-list/data
  [{:vimeo.album/uri "/users/118038002/albums/7670034",
    :vimeo.album/autoplay false,
    :vimeo.album.user/link "",
    :vimeo.album.metadata.interactions.add-logos/uri
    "/users/118038002/albums/7670034/logos",
    :vimeo.album.user.preferences.videos.privacy/view "disable",
    :vimeo.album.user.metadata.interactions.block/uri
    "/me/block/118038002",
    :vimeo.album.user.metadata.connections.channels/total 0,
    :vimeo.album.user.metadata.interactions.follow/added false,
    :vimeo.album.user.metadata.connections.teams/options ["GET"],
    :vimeo.album.user.metadata.connections.folders-root/uri
    "/users/118038002/folders/root",
    :vimeo.album.user.pictures/resource-key
    "9b6cd50b7543a03d77365da646638c8e06f4c7ea",
    :vimeo.album.user.metadata.connections.followers/options ["GET"],
    :vimeo.album.metadata.interactions.add-live-events/options
    ["POST"],
    :vimeo.album.user.metadata.connections.folders/uri
    "/users/118038002/folders",
    :vimeo.album.metadata.connections.videos/uri
    "/albums/7670034/videos",
    :vimeo.album/brand-color nil,
    :vimeo.album.user.metadata.connections.videos/options ["GET"],
    :vimeo.album.privacy/view "anybody",
    :vimeo.album.user.metadata.connections.appearances/total 0,
    :vimeo.album/seo-keywords [],
    :vimeo.album.user.metadata.connections.portfolios/uri
    "/users/118038002/portfolios",
    :vimeo.album/name "Shaaron",
    :vimeo.album.pictures/sizes
    [{:width 100,
      :height 75,
...

@genekim I think you're missing a join:

{[:vimeo.user/id 118038002]
 [{:vimeo.album-list/data [:vimeo.album/uri]}]}

Thanks again for your help, @pithyless! Does anyone have any advice on how to handle paginated response? As shown below, vimeo.album-list includes some information of how many pages are in the total response, URL of the next page, etc… How do people handle this? Do you pass in a page-number to vimeo.album-list? Do you load all the pages by default? (<-- I imagine this would be problematic for many scenarios. I’m imagining an API into Google Photos, which would load 100K entries upon every query. 🙂 Are there any examples you’d point to of how others have handled pagination? Thanks again!

{[:vimeo.user/id 118038002]
 {:vimeo.album-list.paging/previous nil,
  :vimeo.album-list.paging/next nil,
  :vimeo.album-list.paging/last "/118038002/albums/?page=1",
  :vimeo.album-list/per-page 25,
  :vimeo.album-list.paging/first "/118038002/albums/?page=1",
  :vimeo.album-list/id 118038002,
  :vimeo.album-list/page 1,
  :vimeo.album-list/total 8,
  :vimeo.album-list/data [{} {} ...]}

…ah, it looks like the preferred method is passing in a cursor-like thing as a parameter to vimeo.album-list… I’m assuming this is still the case? https://clojurians-log.clojureverse.org/pathom/2018-12-10