feat: global date time formatting through i18n #2552
Merged
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
santhoshvai
reviewed
Jun 13, 2024
santhoshvai
reviewed
Jun 13, 2024
santhoshvai
reviewed
Jun 13, 2024
MartinCupela
approved these changes
Jun 14, 2024
santhoshvai
approved these changes
Jun 17, 2024
|
馃帀 This PR is included in version 5.32.0 馃帀 The release is available on: Your semantic-release bot 馃摝馃殌 |
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.
馃幆 Goal
The goal of the PR is to introduce datetime formatting through i18n in the SDK. This will allow having one source of truth for all date time formatting. Please refer to the doc guide in the same PR to know more about the implementation.
Fixes #2104 as well
馃洜 Implementation details
馃帹 UI Changes
iOS
Android
馃И Testing
鈽戯笍 Checklist
developbranch