关于sap:SAP-Spartacus-internationalization-i18n-翻译问题的排错指南

42次阅读

共计 1054 个字符,预计需要花费 3 分钟才能阅读完成。

有 partners 在应用 SAP Spartacus 进行二次开发时,遇到这个正告音讯:Translation key missing ‘common.search’ in the chunk ‘common’ in file spartacus-core.js

看我的解答:

Hi there,

if you would like to use cxTranslate pipe, make sure you import I18nModule from @spartacus/core and add it in the import section of your AppModule:

Here below is tips about trouble shooting i18n issues.

In my app.module.ts I use B2cStorefrontModule.withConfig to pass my application specific configuration. In Chrome Development Tool, I set breakpoint on line 82:

then in the runtime when the breakpoint is triggered, you can check in debugger, to inspect whether a given translation key, like “common.search” in your case exsts or not. If not exist, you will meet with error message mentioned in this thread.

I am testing based on Spartacus version 2.1 and I didn’t find there is translation key “search” under common chunks, as see in highlighted area above.

I just manually added a custom translation key via:

function provideAdditionaLanguage(translations: TranslationResources) {
translations[“en”].common.common.jerrysearch = “Jerry Search”;
return translations;
}

and configure it in AppModule below:

Then consume it in my page:

final result,it works:

更多 Jerry 的原创文章,尽在:” 汪子熙 ”:

正文完
 0