Multiple graphql endpoints share merged schema (using include to specify module scope)

[sadams]

I'm submitting a...

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

Current behavior

Currently, if i register two graphql endpoints scoped to specific modules (using include: [MyModule]) the schema contains resolvers/types from both modules:
https://github.com/sadams/nestjs-graphql_multiple-endpoints-bug/tree/master
Meaning the schema is incorrect and i can't register two resolvers with the same name under different endpoints.

Expected behavior

Each endpoint should contain resolvers/types specific only to the modules included when registering each path.

Minimal reproduction of the problem with instructions

https://github.com/sadams/nestjs-graphql_multiple-endpoints-bug/tree/master

What is the motivation / use case for changing the behavior?

I need to expose completely separate graphql endpoints in the same application.

Environment

    "@nestjs/common": "6.11.6",
    "@nestjs/core": "6.11.6",
    "@nestjs/graphql": "6.5.4",

For Tooling issues:
- Node version: v10.16.3
- Platform: Mac

[kamilmysliwiec]

Looks like a duplicate of this issue #205

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.