-
Notifications
You must be signed in to change notification settings - Fork 52
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
Generate import report for source language #112
Comments
Can you elaborate on that? The purpose of the report is to show the alignment between source and each target language. What would you you expect to see in the report that only shows the source strings? |
When I run the import, the statistics show 401 errors in the source language and a different number of errors in each of the target languages. That report is different than the report for each of the target languages. The fact that the import indicates errors in the source language, generating a report with those errors in one place that can be easily read makes sense to me, especially because they're different than what's reported in each of the target languages. It seems I should try to resolve the errors and warnings reported in both the source and target languages, before actually doing the import. |
Now with #115:
|
Hi.
When I run
serge import --dry-run
for example, a report for the source language is not generated.A report for the destination languages are generated without issues.
I expected a report to be generated for the source language so I can more easily read through the errors it reported.
Ex.
ERROR: Duplicate key 'MY_DUPLICATE_KEY' found in source file
Thank you.
The text was updated successfully, but these errors were encountered: