Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken Locale Fallback Behavior #8

Open
grantglidewell opened this issue Apr 29, 2022 · 0 comments
Open

Broken Locale Fallback Behavior #8

grantglidewell opened this issue Apr 29, 2022 · 0 comments

Comments

@grantglidewell
Copy link

I see this library has not been updated in 15 Months at the time of filing this issue, this is to document for other potential users.

There are issues with this field application when it comes to localizing at a field level. What is returned from this field in some cases is an empty array for the value and not null. Contentful's fallback logic is weak and evaluates the empty array as a useful value and therefore does not fall back. This is a problem as there are unknown variables that go into when this field produces an empty array for a value. It is somehow related to how field level localization works. One does not have to directly edit and save a field to produce an empty array, but I suspect the field being visible for a locale (ie editing multiple locales in the contentful UI) has some impact.

If this app were to write empty values for keys as null I believe that would mitigate the issue and allow the field level fallback behavior to work as expected.

A tangentially related issue:
contentful/contentful.js#1000

@grantglidewell grantglidewell changed the title Fallback behavior Broken Locale Fallback Behavior Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant