You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The graphcool-binding package allows for a debug argument that logs all GraphQL operations to the console. I think it would be nice to implement it here rather than in the graphcool-binding package so all graphql-binding derivates get access to it.
The text was updated successfully, but these errors were encountered:
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 - GraphQL Mesh has a logging transform that would log each operation, but if you think that something is missing in GraphQL Mesh, please feel free to open a new issue on the GraphQL Mesh repo.
We're looking forward for your feedback of how we can make your experience even better!
The
graphcool-binding
package allows for adebug
argument that logs all GraphQL operations to the console. I think it would be nice to implement it here rather than in thegraphcool-binding
package so allgraphql-binding
derivates get access to it.The text was updated successfully, but these errors were encountered: