title: A same company client has built a graphql api on top of my graphql api
body: <p>I have an in company client which we serve a restAPI endpoint inside our graphql api.</p>
  <p>Using that end point they have created a graphql API which shares most of our logic (they literally copied our resolvers) besides very specific implementations (which include crossing tables and changing certain data before forwarding it).</p>
  <p>We have very close communications with them and I would love it if this silly graphql on top of graphql could be resolved in a way that still keeps my api generic.</p>
  <p>Does anyone have any ideas on how to solve this issue?</p>
  <p>So far I have thought of them having a cross-dependent library which we add to our api and implement under a new endpoint or via the headers of the graphql message but that that's messy with how we manage the resolvers and really hurts the genrality of my project.</p>