Implemented: support to use i18n from dxp and removed app level configuration of i18n(dxp/280) #274
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
R-Sourabh
changed the title
ymaheshwari1
requested changes
Apr 2, 2024
ymaheshwari1
approved these changes
Apr 2, 2024
|
Verified and working fine in release 2.16.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…guration of i18n(#280)
Related Issues
hotwax/dxp-components#280
Short Description and Why It's Useful
Using i18n configuration from the dxp package will help in having a common place to manage configurations related to internationalization
Removed i18n package from the app
Updated all the components and ts file to use translate method from dxp
Screenshots of Visual Changes before/after (If There Are Any)
IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance