Repository navigation
Adding Localization should migrate fields to defaultLocale instead of dropping them #5660
janus-reith
started this conversation in
Feature Requests & Ideas
Replies: 3 comments
|
need this too. currenlty using mongodb, after adding a locale i can fetch the original data by passing in |
0 replies
|
Absolutely needed feature. Migrations should automatically use the default locale and copy that data over instead of dropping it |
0 replies
|
Is there any news on this? I have to localise a field that has a lot of input, for a live website and the client is going to lose all that input? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currrently, when adding localization, fields that now don't match the schema anymore will be dropped (Although there is a warning and it asks for confirmation).
I think it could highly increase DX to offer migrating the current values to the specifed default locale.
Not sure how complicated it is too hook into the current migration logic though.
All reactions