@medrecord/frontend-translations-middleware
Advanced tools
This is a translation middleware for loading and using translations.
This is a translation middleware for loading and using translations.
Add TranslateModule from @ngx-translate/core.
It requires HttpClientModule.
app.module.ts
@NgModule({
...
imports: [
...
HttpClientModule,
TranslationMiddlewareModule.forRoot(),
})
...
],
...
})
export class AppModule { }
Inject TranslationMiddlewareService into your component.
Use method: addTranslation for extending translations list.
Use translationMiddleware instead of translation.
TranslationMiddlewareService
| Method | Description | Default | Values |
|---|---|---|---|
| translations | Getter for displaying all loaded and added translations | {} | -- |
| language | Getter for displaying selected language. | 'en' | 'en','nl','it','fr','es','de' |
| setTranslations | Replace all loaded translations. Custom translations will stay unchanged | -- | - |
| extendTranslations | Extend loaded translations by another load | -- | -- |
| addTranslation | Add custom translation. If key will be same as loaded, this translations will be major. | -- | -- |
| setLanguage | Switch language. It will trigger listenLanguage$ | -- | -- |
| listenLanguage$ | Observable value for getting language updates | -- | -- |
| translate | Get current language translation by key and with params if required. | -- | -- |
If you have no i18n folder in your assets or en.json file you will start getting 404 error in your console. Ignore it or add i18n/en.json as default file.
FAQs
This is a translation middleware for loading and using translations.
We found that @medrecord/frontend-translations-middleware demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Newly introduced telemetry in devenv 1.4 sparked a backlash over privacy concerns, leading to the removal of its AI-powered feature after strong community pushback.
Security News
TC39 met in Seattle and advanced 9 JavaScript proposals, including three to Stage 4, introducing new features and enhancements for a future ECMAScript release.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.