Omitting the info object could put 'promises' into nested fields

[pie6k]

Let's say Post has multiple categories inside categories field.

If you query for - db.query.allPosts() - you'll only get scalar fields.

What do you think about having all nested fields as thenable object

eg:

async function getPostCategories(postId) {
  const post = db.query.post(postId);
  return await post.categories
}

under the hood, categories.then() would be fired, and it could be used to start fetching nested field and in fact return desired data without needing to write info object

Drawback is that you'd have to send 2 requests instead of one.

Note that if given field is not desired, then() of it is not fired, so it's request is not sent.

[schickling]

Hmm this is a really interesting idea! Would you be up to exploring it in a fork? Happy to assist with the implementation.

[Urigo]

Thank you for reporting.

In the last few months, since the transition of many libraries under The Guild's leadership, We've reviewed and released many improvements and versions to graphql-cli, graphql-config and graphql-import.

We've reviewed graphql-binding, had many meetings with current users and engaged the community also through the roadmap issue.

What we've found is that the new GraphQL Mesh library is covering not only all the current capabilities of GraphQL Binding, but also the future ideas that were introduced in the original GraphQL Binding blog post and haven't come to life yet.

And the best thing - GraphQL Mesh gives you all those capabilities, even if your source is not a GraphQL service at all!
it can be GraphQL, OpenAPI/Swagger, gRPC, SQL or any other source!
And of course you can even merge all those sources into a single SDK.

Just like GraphQL Binding, you get a fully typed SDK (thanks to the protocols SDKs and the GraphQL Code Generator), but from any source, and that SDK can run anywhere, as a connector or as a full blown gateway.
And you can share your own "Mesh Modules" (which you would probably call "your own binding") and our community already created many of those!
Also, we decided to simply expose regular GraphQL, so you can choose how to consume it using all the awesome fluent client SDKs out there.

If you think that we've missed anything from GraphQL Binding that is not supported in a better way in GraphQL Mesh, please let us know!

---

In the context of that particular issue - I wonder what you think about the list of dedicated fluent client SDKs I've linked to and if they cover those use case in a better way?

We're looking forward for your feedback of how we can make your experience even better!