Syncing from upstream OCA/server-tools (15.0) #1289
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
remove copyrights from init and update copyrights
* [ADD] restore travis configuration * [PEP] fix pep8 * [REF] exclude product_categ_available_pos of testing due to issue odoo/odoo#23749
Currently translated at 100.0% (11 of 11 strings) Translation: server-tools-12.0/server-tools-12.0-base_jsonify Translate-URL: https://translation.odoo-community.org/projects/server-tools-12-0/server-tools-12-0-base_jsonify/zh_CN/
We can't change the order on ir.export.line since it's used to preserve the order speicifed by the user when creating a export filter into the UI
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: server-tools-12.0/server-tools-12.0-base_jsonify Translate-URL: https://translation.odoo-community.org/projects/server-tools-12-0/server-tools-12-0-base_jsonify/
…atetime object Convert fields.Date and fields.Datetime values to string when serializing to json
…mple field
Before this change, the result of the export of a relational field was always a dict or a list of dict.
ex:
<record id="ir_exp_shopinvader_variant_lang" model="ir.exports.line">
<field name="name">publication_language_id/name</field>
<field name="alias">publication_language_id/name:lang</field>
<field name="export_id" ref="shopinvader.ir_exp_shopinvader_variant" />
</record>
will output:
{
...
"publication_language_id" : {
"lang": "French"
}
...
}
After this change it's now possible to define simple exporter for relational fields where the value into the result will be the display_name or a list of display_name of the related records.
ex:
<record id="ir_exp_shopinvader_variant_lang" model="ir.exports.line">
<field name="name">publication_language_id</field>
<field name="alias">publication_language_id:lang</field>
<field name="export_id" ref="shopinvader.ir_exp_shopinvader_variant" />
</record>
will output:
{
"lang": "French"
}
(Cherry-pick of 652c016 after this commit was dropped by #1894's refactoring)
(+ test so that it cannot be forgotten again)
It could happen that a module adds an ir.export.line for a new field but when tests run the field is not loaded if this module is not a dependency of the module running tests. Furthermore, in general, it seems too strict to break the whole computation if there's a field that is missing. It seems more reasonable to log an error when this happen so that technical action can be taken to fix it.
Co-authored-by: Simone Orsi <[email protected]>
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: server-tools-14.0/server-tools-14.0-base_jsonify Translate-URL: https://translation.odoo-community.org/projects/server-tools-14-0/server-tools-14-0-base_jsonify/
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.
bt_gitbot