[FIX] base: fr translation corrupted import datetime error message #16663
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.
Description of the issue/feature this PR addresses:
When importing data, datetime related errors are corrupted by FR translation.
The source string contains
%%(field)s
variable, but fr translation changed it to%%(fields)s
.This causes weird error :
KeyError : u'fields'
This fix only rename variable to
%%(field)s
in the FR datetime message.Current behavior before PR:
When importing data, when a datetime related error is raised, we only see
u'fields'
on the displayed error messages, nothing more useful.Desired behavior after PR is merged:
When importing data, when a datetime related error is raised, we see the real error :
MM/DD/YYYY does not seem to be a valid datetime for field FIELD
on the displayed error messages.--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr