Required fields for delegated methods

[RobertStigsson]

When doing normal requests (not delegated) we can have Id's without the user needing to call them. With delegated methods, this is not as easy. For example:

Schema1:

User {
   id: String
}

query {
   getAllUsers(): [User]
}

Schema2:

PaymentOption {
   paymentOption: Integer
}

query {
   getPaymentOptions(userId: String): [PaymentOption]
}

SchemaStiching:

extend type User {
  paymentOptions: [PaymentOption]
}

StitchedSchemas:

User {
   id: String
   paymentOptions: [PaymentOption]
}

PaymentOption {
   paymentOption: Integer
}

query {
   getPaymentOptions(userId: String): [PaymentOption]
   getAllUsers(): [User]
}

With this schema (and our resolvers) we can do a query looking like this:

getAllUsers() { 
   id
   paymentOptions 
}

But if we aren't asking for id, our getAllUsers-function wont return any Id's, meaning this query wont return anything:

getAllUsers() {
   paymentOptions
}

Is there any easy way to modify the query that is being delegated to our user-system?

[mfix22]

I believe this question is almost identical to #786. We have some related discussion there.

[yaacovCR]

This may be a duplicate of #786 or you may need to just specify the fragment or new v5 selectionSet hint in mergeSchemas.

Closing for now, feel free to reopen with minimal reproduction if still relevant.