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
Currently angular2's built-in localization library does not support scanning and extracting localization strings from code. Our current success/failure messages come from the code and can't be localized. As a temporary workaround (there is an issue on the angular2 github page to add this) move all success/failure messages from the frontend code to the backend code.
This issue also implies adding string localization to the backend code using standard .net and asp.net core localization functionality.
The text was updated successfully, but these errors were encountered:
Currently angular2's built-in localization library does not support scanning and extracting localization strings from code. Our current success/failure messages come from the code and can't be localized. As a temporary workaround (there is an issue on the angular2 github page to add this) move all success/failure messages from the frontend code to the backend code.
This issue also implies adding string localization to the backend code using standard .net and asp.net core localization functionality.
The text was updated successfully, but these errors were encountered: