Generated schema included all resolvers when using inversifyjs container

[xinghul]

Describe the Bug
Not sure if this is a bug, probably a feature request instead.

I have a use case where I want to separate resolvers into 2 groups: admin resolvers and public resolvers, and generate two different schemas.
However, I noticed that the public schema generate contained all the resolvers(including the private admin resolvers).
Here's the code snippet for generating public schema:

const schema = await TypeGraphQL.buildSchema({
  resolvers: values(publicResolvers),
  emitSchemaFile: {
    path: path.join(__dirname, '../../schema.public.gql'),
    commentDescriptions: true,
  },
});

publicResolvers only contains the public resolvers, but I do have all the resolvers binded to a container(inversifyjs), looks like the container resolvers took precedence, that might be the reason why.

Is there a way to generate the schema based the resolvers passed in?

Thanks!

[MichalLytek]

Please fill the bug report issue form as it may contain valuable info really needed in order to be able to help you.

[MichalLytek]

It's obviously a duplicate of #110 which is fixed in type-graphql@beta, so closing this one 🔒