title: nestJs + gql route conflict/override
body: <p>Hello guys I have an issue with conflicts/overrides inside my nestJS application.</p>
  <p>So what is the issue:</p>
  <p>I Have Resolver A</p>
  <pre class="lang-js prettyprint-override"><code>@Resolver('ResolverA')
  export class SomePageResolver {
    constructor(private readonly someService: someService) {
    }
  
    @Query(() =&gt; someType)
    theThingThatMessesUpStuff(
      @Args('params') params: HttpParamsInput,
      @Context(TokenPipe) authorization: string,
      ): Observable&lt;ActionSetsPageType&gt; {
      return this.someService.doSomething(params, authorization)
    }
  }
  
  </code></pre>
  <p>And a resolver B</p>
  <pre class="lang-js prettyprint-override"><code>@Resolver('ResolverB')
  export class SomePageResolver{
    constructor(private readonly someService: someService) {
    }
  
    @Query(() =&gt; someOtherType)
    theThingThatMessesUpStuff(
      @Args('params') params: HttpParamsInput,
      @Context(TokenPipe) authorization: string,
      ): Observable&lt;ActionSetsPageType&gt; {
      return this.someService.doSomethingElse(params, authorization)
    }
  }
  
  </code></pre>
  <p>Respectively <code>Resolver A</code> is part of <code>Module A</code> and <code>Resolver B</code> is part of <code>Module B</code>.</p>
  <p>Depending on the build I have, there is a chance that both <code>Module A</code> and <code>Module B</code> are imported in a single module (single parent module), which leads to the overwriting issue.
  The essence of the issue is that when both modules are part of the build, if the client makes a query for <code>theThingThatMessesUpStuff</code> it will make a query using the module that is imported last</p>
  <pre class="lang-js prettyprint-override"><code>// some code
  @Module({
    imports: [
      // some imports
      ModuleB,
      ModuleA
    ]
  })
  // some more code
  </code></pre>
  <p>If the example configuration from above is used, whenever the client tries to query <code>theThingThatMessesUpStuff</code> field, the query will be resolved by the implementation inside <code>ModuleA</code>, where for some of the features (inside the front end related to this build) the client will expect the implementation inside <code>ModuleB</code></p>
  <p>And now back to the main question, is there a way without involving too many people, to create a validation that will guarantee, that only unique GQL queries exist in the scope of nestJS application.</p>