graphql-tools
graphql-tools copied to clipboard
:wrench: Utility library for GraphQL to build, stitch and mock GraphQL schemas in the SDL-first approach
As of now when trying to use certain transformers as part of `delegateToSchema` they will fail as the underlying `MapFields` requires `transformSchema` to be called (and `delegateToSchema` only calls the...
**Describe the bug** When running filterSchema it should be keeping the type in its entirety, but it's removing all the fields from the type but keeping the type definition. Running...
https://github.com/ardatan/graphql-tools/pull/2417/files#r554290366
File imports in a master schemata fail to resolve transitive dependencies nested more than one level
**Describe the bug** When 2 GraphQL files are imported in a chain from a starting master schema containing only imports, the dependencies of the imported definitions will not resolve past...
**Is your feature request related to a problem? Please describe.** I want to use a custom graphql implementation. use cases 1. I wanna use @kitten 's [graphql-web-lite](https://github.com/kitten/graphql-web-lite) or something other...
**Describe the bug** When arguments are added to the subscription type on the graphQL schema the requireResolversForArgs is incorrectly erroring. ```graphql type Subscription { numberIncremented(id: Int): Int } ``` `Resolver...
**Is your feature request related to a problem? Please describe.** I've been thinking about the problem I asked about in https://github.com/ardatan/graphql-tools/discussions/3434 and trying to think of ways it could be...
Hello I am working with schema generated from REST endpoint using swagger-to-graphql. It works fine, but all GET operations are mapped as queries, and POST operations as mutations in the...
according to the readme the loader provides only two options: https://github.com/ardatan/graphql-tools/blob/3846041c14d0fe37d43b77156e2a0b85da8651ba/packages/webpack-loader/README.md > noDescription (default: false) - removes descriptions > esModule (default: false) - uses import and export statements instead of...
I am looking to transform a remote schema from something like this: ``` type Client { id: ID! account: Account name: String } type Account { id: ID! value: Int...