Custom object return type & integration with graphql-scalars

[valerii15298]

I have generated resolver which looks like this:

@TypeGraphQL.InputType("EntityUpdateInput", {
  isAbstract: true
})
export class EntityUpdateInput {
  @TypeGraphQL.Field(_type => String, {
    nullable: true
  })
  color?: string | undefined | null;
}

But I wanna change return type to be HexColorCodeDefinition from graphql-scalars. There are examples how to use graphql-scalars with apollo server but I cannot figure it out how to use it with type-graphql especially with typegraphql-prisma. Are there ways to integrate graphql-scalars with typegraphql?

import { HexColorCodeDefinition, HexColorCodeResolver} from 'graphql-scalars';
@TypeGraphQL.InputType("EntityUpdateInput", {
  isAbstract: true
})
export class EntityUpdateInput {
  @TypeGraphQL.Field(_type => HexColorType/*? where to get it ?*/, {
    nullable: true
  })
  color?: string | undefined | null;
}

I see there is possibility to create custom scalars, but it also says:

First of all, we need to create our own GraphQLScalarType instance or import a scalar type from a 3rd-party npm library. For example, Mongo's ObjectId:

So maybe there is some recommended way or example how to use graphql-scalars with type-graphql?

Also I checked graphql-custom-types as described here but graphql-custom-types is not as full featured and as good maintained as graphql-scalars package.

[MichalLytek]

May be related to #43

[valerii15298]

Thanks, @MichalLytek! I should have search for existing issues:)

[valerii15298]

For the input type I did find a solution to omit specific fields from input using TypeGraphQL.omit(input: true) in schema.prisma:

model someModel {
    prop1 String
    /// TypeGraphQL.omit(input: true)
    prop2 String
    @@id(fields: [prop1, prop2])
}

and then extend from generated input type and add custom fields with scalars from graphql-scalars package:

export class GeneratedInput {
  @TypeGraphQL.Field(_type => TypeGraphQL.Int, {
    nullable: false
  })
  prop1!: number;
}

custom:

import { URLResolver } from 'graphql-scalars';
export class CustomInput extends GeneratedInput {
  @TypeGraphQL.Field(_type => URLResolver, {
    nullable: false
  })
  prop2: URL;
}

But in cases for validation, we do not necessary need that because we can use class-validator as @MichalLytek suggested #43