-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
Portal Sprint 3, Portal Sprint 4, Portal Sprint 9, Portal Sprint 9
- Design language/internationalization component in Portal and provide service apis to partnering apps like Policy, VID, SDC, AAI, Usecase UI etc...
- Review the implementation details of the internationalization from Backend and Frontend aspects. We should design or consider about how to handle 1) text or labels on UI components like buttons, form fields; 2) date formats and decimal numbers with comma or period; 3) text/data coming from database tables dynamically.
- The implementation details should consider the current Portal design of Angular Frontend and Spring Backend. Based on the current slide deck attached in the jira, I assume you may lean towards Spring locale (Spring Internationalization i18n). We may need to explore the frontend Angular localization using built-in I18n attributes.
- This impact the on-boarded applications. So, we need to reduce the impact of changes in on-boarded apps by incorporating the internationalization and localization changes into Portal’s SDK. So that at least the applications like Policy, VID etc... which are built using Portal’s SDK can have less impact.