Top type-graphql issues

[Feature request] Resolvers for interfaces

Community Enhancement
samdenty picture samdenty·23 Feb 2019·10 Comments
👍4

Relation between types in resolvers - use an existing resolver to resolve a field

Community Duplicate Enhancement
shlomokraus picture shlomokraus·14 Oct 2018·14 Comments

Differences with typegql + Nest.js integration

Question Solved
tonyxiao picture tonyxiao·9 Aug 2018·14 Comments

property `authChecker` is not defined in type, so I can't use authChecker.

Invalid
diggymo picture diggymo·25 Jan 2020·2 Comments

FieldResolver is too slow

Community Enhancement Solved
sixmen picture sixmen·6 Dec 2019·9 Comments

[RFC] Make class-validator a peer dependency

Community Enhancement Solved
teoxoy picture teoxoy·27 Jun 2019·15 Comments
👍3

Cooperation with graphql-faker

Community Discussion Enhancement
baronTommy picture baronTommy·28 Mar 2019·6 Comments

make resolvers optional to enable a schema-first approach

Discussion Question
soneymathew picture soneymathew·5 Jan 2019·7 Comments

Typed decorators - enhanced type-safety

Discussion Enhancement
MichalLytek picture MichalLytek·3 Jan 2019·4 Comments
❤9 👍2

`@Authorized` in subscriptions

Bug Solved
MichalLytek picture MichalLytek·21 Oct 2018·3 Comments
👍8
 Previous issues
Next issues