TS-Generator: Nullable fields & strict mode

[ryanquinn3]

Description

The generated [Type]Parent interface is compatible with typescript's --strictNullChecks setting if the type includes an optional field. With --strictNullChecks enabled, null and undefined are treated as different values.

The related issue that is now causing the break:
#25

Steps to reproduce

type User {
  name: String
}

type Query {
  user: User
}

Expected results

Should produce a resolver type that allows for undefined values

export namespace UserResolvers {
  export type NameType<T extends ITypeMap> = (
    parent: T['UserParent'],
    args: {},
    ctx: T['Context'],
    info: GraphQLResolveInfo
  ) => string | Promise<string | null | undefined> | null | undefined;

Actual results

export namespace UserResolvers {
  export type NameType<T extends ITypeMap> = (
    parent: T['UserParent'],
    args: {},
    ctx: T['Context'],
    info: GraphQLResolveInfo
  ) => string | Promise<string> | null ;

Versions

• graphql-resolver-codegen: 0.3.1

[ryanquinn3]

This is a duplicate of #50.

Closing.