Have all types and interfaces added to the schema by plugins be automatically namespaced.
Namespacing the schema avoids naming conflicts, which happens when different owners (eg: different teams in the company, or among 3rd party plugins) use the same name for a type or interface.
For instance, let's say that company "AwesomeWP" has the Tutorials and the Sales team, and both of them create a Product type for the company's GraphQL schema, producing a conflict.
By namespacing the schema, the two types would be automatically converted to AwesomeWPTutorialsProduct and AwesomeWPSalesProduct, avoiding the conflict without having to manually modify the schema, or have the teams interact with each other.
The entities from the WordPress data model are not namespaced permalink
The WordPress data model is considered canonical, and its GraphQL schema types (such as Post and User) and interfaces (such as Commentable and WithMeta) are not namespaced.
Namespacing the schema for a custom endpoint or persisted query, can be defined through the corresponding schema configuration:
2. Default mode, defined in the Settings permalink
If the schema configuration has value "Default", it will use the mode defined in the Settings:
Namespacing the schema in the Admin clients permalink
Namespacing the schema in the wp-admin can be selected on the Settings. It will be applied on the GraphiQL and Interactive Schema clients, on the configuration in Access/Cache Control Lists, and possibly on other extensions.