fix: Consistent Date Formatting Across Product, HR, and GroupChat Responses Based on User Locale #297
Conversation
This file contains hidden or 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
UtkarshMishra-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
UtkarshMishra-Microsoft
changed the title
Roopan-Microsoft
approved these changes
Jul 4, 2025
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
blessing-msft
pushed a commit
that referenced
this pull request
Aug 1, 2025
fix: Consistent Date Formatting Across Product, HR, and GroupChat Responses Based on User Locale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Purpose
This PR resolves inconsistent date formatting across Product, HR, and GroupChatManager responses.
All dates now respect the user's desktop locale preference, ensuring a consistent experience.
Introduced utils_date.py as a simple, standalone utility to handle date formatting cleanly.
Removed raw or hardcoded date formats like 2025-07-25 or 03-07-2025.
Backend now produces clean, consistent, locale-aware date formatting in all responses.
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information