[GraphQL] Localisations required when nog enabled on content type

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

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

Is there a way to make the localisations field optional in the GraphQL schema or remove it entirely?

This topic has been created from a Discord post (1286588958289035264) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

1 Like

[GraphQL][Strapi V5] Localisations required when nog enabled on content type

1 Like

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

1 Like

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

1 Like

Hi <@770673551212281917> Could you open an issue on Gtihub so the team can triage it please :man_bowing:

1 Like

Done! [Strapi V5] Localisations required when not enabled on collection type with GraphQL · Issue #21401 · strapi/strapi · GitHub

1 Like

Great thank you