Bug 1930444 - Lost ability to localize timestamps for en-gb locale
Summary: Lost ability to localize timestamps for en-gb locale
Keywords:
Status: CLOSED DUPLICATE of bug 1862084
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.8.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard: Scrubbed
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-18 22:00 UTC by ralpert
Modified: 2021-04-16 15:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-16 15:28:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 8490 0 None open [WIP] Bug 1862084: Consistent formatting of dates and times 2021-04-01 14:45:00 UTC

Description ralpert 2021-02-18 22:00:26 UTC 
Description of problem:
We regressed and lost the ability to localize timestamps for en-gb.

I think it's related to https://github.com/openshift/console/pull/8100. We should explore other options that will allow us to maintain sub-language functionality while minimizing the number of network requests.

Version-Release number of selected component (if applicable):
4.7

How reproducible:
Always.

Steps to Reproduce:
1. Add ?lng=en-gb to the console URL.

Actual results:
Timestamps remain in en format rather than being in en-gb format.

Expected results:
Timestamps are in en-gb format.
Comment 1 Samuel Padgett 2021-03-22 13:48:37 UTC 
We should look at taking a similar approach as in https://github.com/openshift/console/pull/8365 to localizing times. We have https://issues.redhat.com/browse/CONSOLE-2790 open to move away from moment.js.
Comment 2 Samuel Padgett 2021-04-01 14:45:03 UTC 
This will be fixed by https://github.com/openshift/console/pull/8490.
Comment 3 Samuel Padgett 2021-04-16 15:28:44 UTC 
This was fixed as part of bug 1862084.

*** This bug has been marked as a duplicate of bug 1862084 ***
Note You need to log in before you can comment on or make changes to this bug.