fix(richtext-lexical): localized sub-fields were omitted from the API output (#6489)

Closes #6455. Proper localization support will be worked on later, this
just resolves the issue where having it enabled not only doesn't
localize those fields, it also omits them from the API response. Now,
they are not omitted, and localization is simply skipped.
This commit is contained in:
Alessio Gravili
2024-05-24 10:01:04 -04:00
committed by GitHub
parent 3839eb5ab0
commit 7a768144ea
3 changed files with 3 additions and 3 deletions

View File

@@ -40,7 +40,7 @@ export const blockPopulationPromiseHOC = (
fieldPromises,
fields: block.fields,
findMany,
flattenLocales,
flattenLocales: false, // Disable localization handling which does not work properly yet. Once we fully support hooks, this can be enabled (pass through flattenLocales again)
overrideAccess,
populationPromises,
req,

View File

@@ -40,7 +40,7 @@ export const linkPopulationPromiseHOC = (
fieldPromises,
fields: props.fields,
findMany,
flattenLocales,
flattenLocales: false, // Disable localization handling which does not work properly yet. Once we fully support hooks, this can be enabled (pass through flattenLocales again)
overrideAccess,
populationPromises,
req,

View File

@@ -64,7 +64,7 @@ export const uploadPopulationPromiseHOC = (
fieldPromises,
fields: props?.collections?.[node?.relationTo]?.fields,
findMany,
flattenLocales,
flattenLocales: false, // Disable localization handling which does not work properly yet. Once we fully support hooks, this can be enabled (pass through flattenLocales again)
overrideAccess,
populationPromises,
req,