Working with interface types resolvers

[ScreamZ]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ x ] Feature request
[ x ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

I would like to define resolvers for interface types, which are normally not allowed.

Currently, I'm doing this to handle those cases:

For those who want more about it, read my initial issue at https://stackoverflow.com/questions/61867673/nestjs-x-graphql-x-typegoose-issue-on-sub-resolver

// One annotation per things that implement my CurrentUserDTO interface
@Resolver(() => IndividualUserDTO)
@Resolver(() => ProfessionnalUserDTO)
export class CurrentUserDTOResolver {
  constructor(
    private readonly supplierService: SupplierService,
    private readonly volunteerService: VolunteerService,
    private readonly productService: ProductService,
  ) {}

  @ResolveField(() => [Supplier])
  async suppliers(@Parent() user: CurrentUserDTO) {
    return user.suppliers.length > 0
      ? this.supplierService.find({ _id: { $in: user.suppliers } })
      : [];
  }
}

Interrogation

While this is working great, I would like to be sure I'm not hacking the library in terms of practice to make this work

I saw that an inheritResolversFromInterfaces property exists in apollo https://www.apollographql.com/docs/apollo-server/api/apollo-server/#makeexecutableschema

But I can't figure out how to use it in NestJS… Maybe you could help me? Look like it's not implemented to pass args to makeExecutableSchema

Environment

➜ yarn list --depth=0 --pattern nest
yarn list v1.22.4
├─ @nestjs/cli@7.1.4
├─ @nestjs/common@7.0.9
├─ @nestjs/config@0.4.0
├─ @nestjs/core@7.0.9
├─ @nestjs/graphql@7.3.5
├─ @nestjs/jwt@7.0.0
├─ @nestjs/mapped-types@0.0.3
├─ @nestjs/passport@7.0.0
├─ @nestjs/platform-express@7.0.9
├─ @nestjs/schematics@7.0.0
├─ @nestjs/testing@7.0.9
└─ nestjs-typegoose@7.1.22

[kamilmysliwiec]

I would like to define resolvers for interface types, which are normally not allowed.

It's impossible to define resolvers for interface types (in general).

[ScreamZ]

Figured out later, thanks

[dberardo-com]

is this still an issue ? does the flag inheritResolversFromInterfaces have any meaning ?