Thanks for the answer.
From an API perspective, this is less than ideal, as a developer I’d expect that setting a top level locale variable would affect all the content in the query, like it’s for most other Headless CMS (e.g. when using with Next.js, everything else is a huge pain). If you have e.g. a look at DatoCMS, the whole GQL query gets localized, which, IMO, should be the default behavior when using such an API. Also, the Accept-Language header should be taken into account for those queries. As the GQL resolvers aren’t directly correlated with the DB structure underneath, this shouldn’t be too hard to implement. If that’s more suitable, I could open an issue in GH and try to prepare a PR.