Comments (3)
That is something we definitely want to build soon! I like the variable syntax. Another use-case are the Prisma subscriptions, when you only want to return the node
.
from graphql-binding.
There are a couple of GraphQL primitives to consider before going for this approach:
Fragments
Inline Fragments
If the original query contains inline fragments, they need to be properly copied over to the new resulting info object.
Global Fragment definitions + fragment spread
Not just the normal selection set must be taken care of, but also globally defined fragments on types (and all related fragments) + the fragment spread that is being used in the relevant sub-selection.
Variables
The resulting query must include the incoming variables, but still support extending the variables with the bindings.
Arguments
The arguments and variables need to be properly propagated to the resulting query document.
A big challenge here is how to provide arguments for sub fields.
Aliases
As soon as aliases are involved, the response cannot be storngly typed anymore, as a field could have any name.
Name clashes
Both in the delegation as in variables/args, there could be name clashes.
We need a clear definition, which API gets precedence over the other.
from graphql-binding.
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 would love to hear your thought on our transform
API and the currently available transforms to see how your query would look like with 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!
from graphql-binding.
Related Issues (20)
- Support webpack and other bundlers HOT 2
- typescript schema import breaks HOT 6
- Subscriptions are broken on 2.2.2 HOT 1
- Error when calling mutation that is specified inside "extend type Mutation" block HOT 4
- Experiment: using graphql-binding in client-side HOT 5
- Context object not getting sent HOT 2
- Is it possible to use batching? HOT 1
- How to dynamically update the link headers in the binding instance ? HOT 6
- Cannot use Alias with custom binding HOT 2
- [object Object] is returned from a binding when resolver throws an error HOT 14
- method cache and memory leaks HOT 3
- Cannot find module 'graphql/tsutils/Maybe' HOT 5
- mkdirp is not a function HOT 2
- mkdirp race condition HOT 4
- error data from binding is not available HOT 5
- How to write dynamic fragment to use with addFragmentToInfo
- Error with 'fs' and 'module' modules in front end HOT 1
- How can i custom resolves query connection which i expose from "forwardTo" HOT 1
- A new path for graphql-binding - help us decide on the roadmap! HOT 10
- Dependency Dashboard
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graphql-binding.