[Strapi V5] Localisations required when not enabled on collection type with GraphQL

[jelmer-visser]

Bug Report

We use GraphQL in our Next.js application along with codegen to generate types based on the GraphQL schema and queries. In Strapi v5, we have a collection type where localization is disabled, but in the GraphQL schema, the localizations field is still marked as required.

When I include the localizations field in my query, it triggers the same error on the subsequent localizations field (possibly due to a circular dependency).

System Information

• Node.js version: 18.20.4
• NPM version: 10.7.0
• Strapi version: 5.0.0
• Database: MySQL
• Operating System: macOS (darwin-arm64)
• Project Language: TypeScript

Steps to Reproduce

1. Enable the GraphQL plugin in Strapi v5.
2. Create a collection type with localization disabled.

While the following steps might not be necessary to trigger the issue, they reflect our specific setup:

3. Create a component that uses the collection type as a relation.
4. Add this component to a Dynamic Zone.
5. Create a GraphQL query that queries the component in the dynamic zone
6. Run codegen in Next.js to generate types.ts.
7. Use the generated type in your application and build the Next.js project.
8. You will encounter an error stating that localizations is required, despite being disabled.

Expected Behavior

When localization is disabled, the localizations field should not be required in the query.

Screenshots

In the screenshot below, the localizations field is marked as required, even though it is disabled for blogs:

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/graphql-localisations-required-when-nog-enabled-on-content-type/46445/6