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

[IMP] base: do not set a value for new translations #24391

Closed

Conversation

mart-e
Copy link
Contributor

@mart-e mart-e commented Apr 24, 2018

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

@mart-e mart-e added RD research & development, internal work Framework General frontend/backend framework issues labels Apr 24, 2018
@mart-e mart-e requested a review from rco-odoo April 24, 2018 10:10
@mart-e mart-e force-pushed the master-insert-new-trad-no-value-mat branch from 1a6c558 to 5887a6c Compare September 3, 2018 14:59
@mart-e mart-e requested a review from xmo-odoo September 3, 2018 15:16
Copy link
Member

@rco-odoo rco-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@d-fence d-fence left a 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.

@robodoo robodoo added the r+ 👌 label Sep 3, 2018
@xmo-odoo xmo-odoo removed their request for review September 3, 2018 15:36
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
@robodoo robodoo removed the r+ 👌 label Sep 4, 2018
d-fence
d-fence previously requested changes Sep 4, 2018
Copy link
Contributor

@d-fence d-fence left a 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.

Copy link
Contributor

@d-fence d-fence left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 👍

@robodoo robodoo added the r+ 👌 label Sep 4, 2018
@robodoo
Copy link
Contributor

robodoo commented Sep 4, 2018

Unable to stage PR (merge conflict)

@robodoo robodoo added error 🙅 and removed r+ 👌 labels Sep 4, 2018
@mart-e
Copy link
Contributor Author

mart-e commented Sep 4, 2018

robodoo 🤖 retry !

robodoo pushed a commit that referenced this pull request Sep 4, 2018
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
@robodoo robodoo added CI 🤖 Robodoo has seen passing statuses r+ 👌 and removed error 🙅 labels Sep 4, 2018
@robodoo
Copy link
Contributor

robodoo commented Sep 4, 2018

Merged in d65969d

@xmo-odoo
Copy link
Collaborator

xmo-odoo commented Sep 4, 2018

🎉 🎉 🎉 🎉 🎉

@jem-odoo
Copy link
Contributor

jem-odoo commented Sep 4, 2018

Congrat's !!
Is the developper suppose to delete his branch, or robodoo will do it ? :p

@xmo-odoo
Copy link
Collaborator

xmo-odoo commented Sep 4, 2018

Is the developper suppose to delete his branch

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).

@mart-e mart-e deleted the master-insert-new-trad-no-value-mat branch September 4, 2018 11:23
switch87 pushed a commit to odoo-dev/odoo that referenced this pull request Sep 25, 2018
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
VincentSchippefilt pushed a commit to odoo-dev/odoo that referenced this pull request Feb 7, 2019
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI 🤖 Robodoo has seen passing statuses Framework General frontend/backend framework issues RD research & development, internal work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants