Adding @Undocumented decorator to prevent Query/Mutation/Subscription from getting generated in SDL

[bneigher]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

When making services that are part of a Federated Apollo Gateway, it would be nice to control which Operations are not to be generated with the code-first approach... which subsequently is to be printed with printSchema or printSchemaWithDirectives

Because Apollo Federated Gateway doesn't support Subscriptions, for example, attempting to publish a SDL .grahpql with Subscriptions results in an error...

By hiding some Operations from the printed out SDL file, additional functionalities could still be exposed from the GQL downstream service (obviously without stitching support)

Describe the solution you'd like

If there was a directive @Undocumented used like illustrated below:

@Undocumented()
@Subscription(() => [Model])
modelTopic() {
   return this.pubSub.asyncIterator('modelTopic')
}

We could maintain this Subscription as a feature of the service, while essentially not informing the Gateway of it's existence since the SDL wouldn't have been generated with:

schema {
  query: Query
  mutation: Mutation
  subscription: Subscription <-- DELETED
}

type Subscription {          <-- DELETED
  bookingsTopic: [Booking!]! <-- DELETED
}                            <-- DELETED

Teachability, documentation, adoption, migration strategy

No response

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

To encourage the use of gql Subscriptions with limited capabilities of the federated GQL services

[kamilmysliwiec]

We could maintain this Subscription as a feature of the service, while essentially not informing the Gateway of it's existence since the SDL wouldn't have been generated with:

If it's not supposed to be exposed in the schema, why can't you just comment out the @Subscription decorator?

[bneigher]

@kamilmysliwiec well, because I want to Subscription handler to be available when directly using the GQL API ☝️ ... but not federated into the Apollo Gateway when updating the generated SDL. I feel like my ask is more of an ability to remove things from the SDL when we printSchema