Fix localization bug with Insider Build #2775
Merged
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.
In the current Insider Build, even when you switch the language, the translations still display in English. This is because after the OneLocBuild task is run, then
npm run clean
andnpm run build-translations
are run in succession in Build & Pack. (Essentially all language translations are built, then all cleaned out, then only English is built.)This PR fixes this issue by getting rid of
clean:resources
(which isn’t really needed anyways since the translation files are overwritten/updated on every new build). Now the translations will stay and won’t immediately be cleaned out once built.This PR also solves the error of the translation ID appearing when you switch the language to something non-English. Before, if a string in a non-English language didn’t have a translation, it would show the ID (e.g.
application.buttons.editor
). Now, it shows the English string instead (Editor
).