I have a theoretical question. Let's say I have the need to do 2 different GraphQL APIs. Let's call them, for simplicity:

• public/graphql
• private/graphql

So, in this scenario, I would like to expose some data, both in types and inputs, on the private/graphql endpoint BUT NOT on the public one. I'll do a quick example.

Let's say I have a type User, like this:

type User {
 user_id: ID
 name: String
 surname: String
}

So on private/graphql I would like that one can query for the full User type, including the user_id. On the public/graphql endpoint, though, I want that people can query just for name and surname.

Defining two different types for this simple differentiation seems like an overkill to me. I mean, there should be a smarter way to do this, without having to declare yet another type.

Same thing for inputs. Where there is the need, for a given endpoint to be able to input all the fields, for some other, a subset of the fields.

I know GraphQL "likes" static schemas. And that's ok..in fact here I would like to make two static schemas, but without having to repeat myself over and over with the types and the inputs.

Any cool ideas?