graphql-fields icon indicating copy to clipboard operation
graphql-fields copied to clipboard

Turns GraphQLResolveInfo into a map of the requested fields

Results 16 graphql-fields issues
Sort by recently updated
recently updated
newest added

Hey, your library is simple, small and efficient. It would be great if you continue to maintain it. Let me know if you need any help with it.

I have a problem. Currently my company is incorporating this at the top level of a component during unit tests like so: `... import { GraphQLFieldsReturnType } from '../../../type-defs'; jest.mock('graphql-fields',...

Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. Commits 7efb22a 1.2.6 ef88b93 security notice for additional prototype pollution issue c2b9819 isConstructorOrProto adapted from PR bc8ecee test from prototype pollution PR See full...

dependencies

I am looking to use this module in a TypeScript project and feel the usability would greatly improve with type definitions. Considering how small and self-contained the module is, I...

Hello here, is there any example that shows how to use this with buildSchema?

like `{ processArguments: true }`, add a new option like `{extensions: true}`. and will add `__extenstions` property and maybe shall be another property like `__leaf` to tell if it reaches...

## Issue Default argument values defined in GraphQL Schema Language are not respected (when using the processArguments option). ## Example Schema: ```graphql type Bucket { id: ID, count: Int, }...

I think the current API for this package is limiting in several use cases: * arguments * supporting the same field queried multiple times via aliases * fields queried on...

A single input value on a field that should be a list is coerced to a list [according to the Graphql spec](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System.List). > Expected Type | Provided Value | Coerced...