Skip to content
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

How do i18n json files get read for a custom renamed examples component #489

Open
peterclemenko opened this issue Sep 12, 2019 · 3 comments

Comments

@peterclemenko
Copy link

So I'm trying to create a new component based on examples called "workspace". In workspace.module (renamed from examples) I added workspace instead of examples as the path, and copy pasted the folder as workspace. When I try to use the new tabs though, the tabs show as the i18n names rather than the translated/proper captions. There has to be something I'm missing. Any suggestions?

export function HttpLoaderFactory(http: HttpClient) {
return new TranslateHttpLoader(
http,
${environment.i18nPrefix}/assets/i18n/workspace/,
'.json'
);
}

@tomastrajan
Copy link
Owner

Pfuu, hard to say like this, must be something missing, wish you good luck with the hunt!

@peterclemenko
Copy link
Author

I don't know why it's broken on the sub localization files, but moving the localization to the main localization did the trick. Not sure if I should close this.

@ghost
Copy link

ghost commented Oct 29, 2019

Same thing happened to me and I just renamed the folders examples into tabs and replaced all the instances of "Examples" with "Tabs" etc.

EDIT: If anyone else is struggling with this, be sure to include the renamed Tabs(Examples)Effects in the EffectsModule.forFeature() array:

EffectsModule.forFeature([TabsEffects, the tab compnents following])

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants