Currently, when using GraphQL to query a node, the lang argument takes a list of languages. However, this list is not inherited to lookups in the fields, instead all node queries in the fields only use the one language that was the first match (unless overwritten, which is only possible for nodes, but not for node lists - cf #207).
Example use case: a multi-language node has a field of type Node/binary_content. The latter is only available in one language.
Currently, when using GraphQL to query a node, the
langargument takes a list of languages. However, this list is not inherited to lookups in the fields, instead all node queries in the fields only use the one language that was the first match (unless overwritten, which is only possible for nodes, but not for node lists - cf #207).Example use case: a multi-language node has a field of type Node/binary_content. The latter is only available in one language.