The GraphQL developer incorporated a field that should not be available for introspection or validation by the client. How would the API developer…

In IBM API Connect, the @hide directive is the designated method for modifying a GraphQL schema to prevent specific fields or types from being exposed to the client. Applying this directive to a field in the schema definition ensures that it is omitted from the schema served by the API gateway. Consequently, the field will not appear in introspection queries and will be rejected by the validator if a client attempts to include it in a query, effectively hiding it.

1. IBM. (2023). Creating a GraphQL API proxy. IBM Documentation. Retrieved from https://www.ibm.com/docs/en/api-connect/10.0.5.x?topic=apis-creating-graphql-proxy-api. In the section "Editing a GraphQL schema

" the documentation states: "You can use the @hide directive to remove types or fields from the schema."

2. IBM. (2023). GraphQL policies. IBM Documentation. Retrieved from https://www.ibm.com/docs/en/api-connect/10.0.5.x?topic=reference-graphql-policies. This page details the Redaction policy

explaining its function is to "Redact specified fields in the GraphQL response object

" which confirms it acts on the response data

not the schema definition for introspection.