graphql-js

graphql-js copied to clipboard

object validation creates misleading non null error

12

# What is happening A non null error is reported for a field that is not null, e.g. `Cannot return null for non-nullable field Account.id.` # What is really happening...

mschipperheyn

Allow to specify field type as a string

12

## Currently graphql.js expects `type` option to be an instance of GraphQLType (`GraphQLInputObjectType`, `GraphQLObjectType`, etc). Example: ```js const AnotherType = new GraphQLObjectType({ ... }) const Type = new GraphQLObjectType({ name:...

stalniy

Add utility function function for generating fully-featured schema from SDL

3

With SDL [officially](https://github.com/graphql/graphql-spec/pull/90) part of the specification, would it be worthwhile to provide a way to build a build a fully-featured schema from a Document AST? Currently, schemas built using...

danielrearden

Handlers for custom directives

1

Hi. Seems that there is no way to handle custom directives. This issue was created at @IvanGoncharov's [request](https://github.com/graphql/graphql-js/issues/41#issuecomment-490044071). I use [graphql-faker](https://github.com/APIs-guru/graphql-faker) to define schemas with fake data. Frontend developers feel...

xamgore

Add field directives on Info

3

It's possible to add a new field on info with the directives of that field? ### Reason: The main reason for this is that using a `fieldResolver` it'll be possible...

estrada9166

Large memory allocations and very slow execution when type errors occur in complex inputs

6

Hi, We have a rather large complex object as an input. A single request with hundreds of type errors in the input took 9 seconds in `graphql.execute`. The majority of...

SoyYoRafa

Subscriptions do not work with asynchronous resolver function

6

I noticed that the `subscribe` function does not work properly when it is used with an asynchronous field resolver function. Also, there is no unit test for this case. This...

Cito

Mutation validates when schema does not support mutations

7

graphql-js currently considers the following bogus operation valid against the given schema: ```graphql # schema: type Query { f: String } # operation: mutation { bogus } ``` In particular,...

benjaminjkraft

schema assumeValid flag has two meanings

4

Currently, if I understand the flow correctly, to skip schema validation during an execute call, one must create a schema with the `assumeValid` option (as opposed to an explicit execute...

yaacovCR

Feature Request: Allow interfaces to resolve to other interfaces

2

I originally raised this in [Apollo Server](https://github.com/apollographql/apollo-server/issues/5630) and was told that it's actually implemented here. Suppose I have the following schema: ``` interface Node { id: ID! } interface Product...

SleeplessOne1917