You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
I have been using your library for my application as a solution to handling translating dynamic text using the translate pipe approach. My concerns at this point is that we also have some static text that is also going to need to be translated dynamically based on the user selecting a desired language via a dropdown menu. Based on my knowledge on using async pipe everywhere might lead to a performance hit or maybe an issue of race conditions. My question would be to you is there any issues with using a combination of pipes, services AND the xi18n from angular CLI?
thanks in advance.
The text was updated successfully, but these errors were encountered:
Right now I am using one file for each module. I wanted to break this down into one file per component. This way I could server up the files in a jsdoc or confluence. If a module (for example SharedModule) had multiple components in it each with a template file with hard coded files in them could I make "en.json" files for each of them?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
I have been using your library for my application as a solution to handling translating dynamic text using the translate pipe approach. My concerns at this point is that we also have some static text that is also going to need to be translated dynamically based on the user selecting a desired language via a dropdown menu. Based on my knowledge on using async pipe everywhere might lead to a performance hit or maybe an issue of race conditions. My question would be to you is there any issues with using a combination of pipes, services AND the xi18n from angular CLI?
thanks in advance.
The text was updated successfully, but these errors were encountered: