How to handle JSON with nested resources?

[angristan]

With the usual example of response: (https://jsonplaceholder.typicode.com/users/1/posts)

[
  {
    "userId": 1,
    "id": 1,
    "title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
    "body": "quia et suscipit\nsuscipit recusandae consequuntur expedita et cum\nreprehenderit molestiae ut ut quas totam\nnostrum rerum est autem sunt rem eveniet architecto"
  },
  {
    "userId": 1,
    "id": 2,
    "title": "qui est esse",
    "body": "est rerum tempore vitae\nsequi sint nihil reprehenderit dolor beatae ea dolores neque\nfugiat blanditiis voluptate porro vel nihil molestiae ut reiciendis\nqui aperiam non debitis possimus qui neque nisi nulla"
  }
]

the schema can nicely be:

schema
  @server(port: 8000)
  @upstream(baseURL: "http://jsonplaceholder.typicode.com") {
  query: Query
}

type Query {
  users: [User] @http(path: "/users")
}

type User {
  id: Int!
  name: String!
  username: String!
  email: String!

  posts: [Post] @http(path: "/users/{{.value.id}}/posts")
}

type Post {
  id: Int!
  title: String!
  body: String!
}

However if the response is of this format:

{
  "posts": [
    {
      "userId": 1,
      "id": 1,
      "title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
      "body": "quia et suscipit\nsuscipit recusandae consequuntur expedita et cum\nreprehenderit molestiae ut ut quas totam\nnostrum rerum est autem sunt rem eveniet architecto"
    },
    {
      "userId": 1,
      "id": 2,
      "title": "qui est esse",
      "body": "est rerum tempore vitae\nsequi sint nihil reprehenderit dolor beatae ea dolores neque\nfugiat blanditiis voluptate porro vel nihil molestiae ut reiciendis\nqui aperiam non debitis possimus qui neque nisi nulla"
    }
  ],
  "meta": {
    "page": 1,
    "per_page": 10,
    "total": 2,
    "total_pages": 1
  }
}

Then I'm able to get the info like this:

schema
  @server(port: 8000)
  @upstream(baseURL: "http://jsonplaceholder.typicode.com") {
  query: Query
}

type Query {
  users: [User] @http(path: "/users")
}

type User {
  id: Int!
  name: String!
  username: String!
  email: String!

  posts: PostsResponse @http(path: "/users/{{.value.id}}/posts")
}

type PostsResponse {
  posts: [Post]
  # meta: Meta
}

type Post {
  id: Int!
  userId: Int!
  title: String!
  body: String!
}

But it's leaking the underlying API call. Is there a wat to basically jq .posts to be able to get the first schema with the second JSON response?

[angristan]

I feel like this is also why batching can't work in this case? (response.posts.[].userId needs to be matched to the User ID, vs response.[].userId in the supported case)

[angristan]

Opened issue for this one: #2489

[tusharmath]

@angristan The issue is fixed. We made a few changes internally on the batching algorithm it should work in the latest release. Thanks for pointing out!

[angristan]

I think what i'm looking for is a bit like the @addField directive. Something like:

schema
  @server(port: 8000)
  @upstream(baseURL: "http://jsonplaceholder.typicode.com") {
  query: Query
}

type Query {
  users: [User] @http(path: "/users")
}

type User {
  id: Int!
  name: String!
  username: String!
  email: String!

  posts: [Post] @http(path: "/users/{{.value.id}}/posts") @select(path: "posts")
}

type Post {
  id: Int!
  userId: Int!
  title: String!
  body: String!
}

(considering this payload:

{
  "posts": [
    {
      "userId": 1,
      "id": 1,
      "title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
      "body": "quia et suscipit\nsuscipit recusandae consequuntur expedita et cum\nreprehenderit molestiae ut ut quas totam\nnostrum rerum est autem sunt rem eveniet architecto"
    },
    {
      "userId": 1,
      "id": 2,
      "title": "qui est esse",
      "body": "est rerum tempore vitae\nsequi sint nihil reprehenderit dolor beatae ea dolores neque\nfugiat blanditiis voluptate porro vel nihil molestiae ut reiciendis\nqui aperiam non debitis possimus qui neque nisi nulla"
    }
  ],
  "meta": {
    "page": 1,
    "per_page": 10,
    "total": 2,
    "total_pages": 1
  }
}

)

[angristan]

Which is maybe what the JQ integration could have achieved: #1321

[tusharmath]

JQ implementation turned out to be significantly slower than JS so we dropped it. You could consider using JS instead of JQ for most cases. I think in the above case you can use addField

[tusharmath]

@angristan Please try — https://github.com/tailcallhq/tailcall/releases/tag/v0.97.0

[angristan]

Thanks, but I'm not able to make this work (#2495 (comment))

Moreover, I've unmarked this as the answer since this discussion was intially about extracting the response (#2471 (comment)) like what was proposed in #2497

[tusharmath]

@angristan Were you able to try with the latest release? Can you specify a repro for this with the exact tailcall version with the actual vs expected.