You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Resx Manager fails to import all translations when the neutral resource file have been deleted, but there still is a localized version.
MyResource.resx
MyResource.da.resx
To Reproduce
Create a resource file with a single row
Translate the row to another language
Export an Excel file of all rows
Delete the neutral resx file
Import the Excel file
Expected behavior
I would expect the ResxManager to skip importing the translation, similar to how it works if all the Resource files are deleted.
I tried debugging this a bit, but I was unable to detect where I would need to make my changes.
But I believe the primary culprit is here:
I agree its messed up, but it can happen when you have multiple developers and translators working in the same project on multiple branches. My real life case was that a developer deleted a section of the application (including translations), but our translator had already exported an excel file because they where adding a new language.
Honestly what was bugging me the most was the error message "Import failed partially. Some columns have been already imported, but not all." it provided no helpful hint on what was wrong.
Maybe listing what imports failed in the "output" tab would be helpful?
Describe the bug
Resx Manager fails to import all translations when the neutral resource file have been deleted, but there still is a localized version.
MyResource.resxTo Reproduce
Expected behavior
I would expect the ResxManager to skip importing the translation, similar to how it works if all the Resource files are deleted.
I tried debugging this a bit, but I was unable to detect where I would need to make my changes.
But I believe the primary culprit is here:
ResXResourceManager/src/ResXManager.Model/ResourceEntityExtensions.cs
Lines 204 to 218 in 647beb3
The text was updated successfully, but these errors were encountered: