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
[IMP] base: do not set a value for new translations #24391
Conversation
1a6c558
to
5887a6c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Really Good. I will not break your knees this time.
When generating new translations (e.g. 'edit translations' button on a view or on a translatable field), the new generated translations have the source as translation value. Set the state to 'to_translate' as it is the default value This change requires to add a fallback in web_editor when computing translated dom When a translation has no value, there is a fallback done in the different translation method (e.g. xml_translate) but, as the node was manually created in edit_translation_mapping, the fallback was missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be better to have only one commit.
8055fb5
to
17d2e83
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice 👍
Unable to stage PR (merge conflict) |
robodoo 🤖 retry ! |
When generating new translations (e.g. 'edit translations' button on a view or on a translatable field), the new generated translations have the source as translation value. Set the state to 'to_translate' as it is the default value This change requires to add a fallback in web_editor when computing translated dom When a translation has no value, there is a fallback done in the different translation method (e.g. xml_translate) but, as the node was manually created in edit_translation_mapping, the fallback was missing closes #24391
Merged in d65969d |
🎉 🎉 🎉 🎉 🎉 |
Congrat's !! |
Yeah. robodoo doesn't have a kill order/feature, it closes the PRs best as it can but it doesn't remove the branches. Maybe eventually (we'll see as we use it). |
When generating new translations (e.g. 'edit translations' button on a view or on a translatable field), the new generated translations have the source as translation value. Set the state to 'to_translate' as it is the default value This change requires to add a fallback in web_editor when computing translated dom When a translation has no value, there is a fallback done in the different translation method (e.g. xml_translate) but, as the node was manually created in edit_translation_mapping, the fallback was missing closes odoo#24391
When generating new translations (e.g. 'edit translations' button on a view or on a translatable field), the new generated translations have the source as translation value. Set the state to 'to_translate' as it is the default value This change requires to add a fallback in web_editor when computing translated dom When a translation has no value, there is a fallback done in the different translation method (e.g. xml_translate) but, as the node was manually created in edit_translation_mapping, the fallback was missing closes odoo#24391
When generating new translations (e.g. 'edit translations' button on a view or
on a translatable field), the new generated translations have the source as
translation value.
Set the state to 'to_translate' as it is the default value