Open justinmk3 opened 3 years ago
call nls.loadMessageBundle() directly in modules instead
Yup this is a requirement for NLS. Indirect calls would result in the consuming module looking for a localization file named after the imported module/file. But the localize
calls would still be extracted using the current module name, so the module never finds anything.
Problem
vscode extension host sometimes reports warnings of the form:
Solution?
Haven't confirmed, but based on https://github.com/microsoft/vscode/issues/42426 / https://github.com/microsoft/vscode-node-debug/commit/4d9a3a70fb776e05df218849a68cdfd2645d4ed0 we may need to do:
nls.loadMessageBundle()
directly in modules instead of usingsrc/shared/utilities/vsCodeUtils.ts:localize()
src/shared/utilities/vsCodeUtils.ts:localize()