feat: change i18n configuration method #190
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nshenderov
added a commit
that referenced
this pull request
Dec 12, 2024
Changes the localization behavior to apply only for fields explicitly marked as localized (those with "Enable localization for this field" enabled in the Content-Types Builder). The previous logic, which applied localization automatically when i18n was detected (unless ignorei18n was set to true), has been replaced. BREAKING CHANGE: Localization is no longer applied automatically for all fields when i18n is detected. It now applies only to fields explicitly configured for localization in the Content-Types Builder.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
Updates the localization configuration logic for the field.
Instead of automatically applying localization whenever i18n is detected (unless ignorei18n is set to true), it will now apply only to fields explicitly marked as localized (those with the "Enable localization for this field" checkbox enabled in the Content-Types Builder).
Why is it needed?
The previous logic is outdated for the latest Strapi versions.