Top graphql-code-generator issues

[TypeScript Resolvers] Resolvers returned data type cannot be introspected

bug plugins
swcarlosrj picture swcarlosrj·1 Jan 2019·10 Comments

`typescript-resolvers` with noNamespace generates conflicting resolvers name

bug plugins
leonardfactory picture leonardfactory·18 Dec 2018·3 Comments

Mapper types don't apply everywhere they should for typescript-resolvers

bug plugins waiting-for-release
SirensOfTitan picture SirensOfTitan·13 Dec 2018·7 Comments

V0.15.0 `typescript-resolvers` plugin generates non-existing Resolver interfaces with noNamespaces

bug plugins waiting-for-release
Rachnerd picture Rachnerd·13 Dec 2018·4 Comments

Extraneous import GraphQLScalarTypeConfig

bug plugins waiting-for-release
mszczepanczyk picture mszczepanczyk·10 Dec 2018·3 Comments

Using graphql-tag inside an Angular Component throws duplicated fragment/query error

bug core waiting-for-release
kroeder picture kroeder·5 Dec 2018·5 Comments

--watch throws "Watchman: Watchman was not found in PATH error."

bug core
Rachnerd picture Rachnerd·3 Dec 2018·1 Comments
👍2

Custom plugin script can't be found

bug core waiting-for-release
kroeder picture kroeder·23 Nov 2018·9 Comments

Error scanning files for graphql`` syntax

bug core waiting-for-release
Jontem picture Jontem·19 Nov 2018·4 Comments
👍1

fragments don't work with noGraphqlTag (apollo-angular)

bug plugins waiting-for-release
mark-buer picture mark-buer·12 Nov 2018·4 Comments
 Previous issues
Next issues