Fix date formatting by stitesExpensify · Pull Request #56124 · Expensify/App

stitesExpensify · 2025-01-30T23:30:30Z

Explanation of Change

We were trying to do hours:month instead of hours:minutes 😂

Fixed Issues

$#56069
PROPOSAL:n/a

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

Book a new trip via expensify travel
Go to the trip room
Make sure that the departure time is correct

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2025-01-30T23:30:40Z

@dominictb @sakluger One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

OSBotify · 2025-01-30T23:33:13Z

A preview of your ExpensifyHelp changes have been deployed to https://db3d1863.helpdot.pages.dev ⚡️

stitesExpensify · 2025-01-31T17:21:28Z

@dominictb can you please go through the reviewer checklist when you get a chance?

sakluger · 2025-01-31T18:23:30Z

Removing my reviewer assignment because this is not Help Site related.

…nto stites-fixDateFormatting

…rmatting

dominictb · 2025-02-03T16:08:59Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

dominictb · 2025-02-03T16:35:54Z

@stitesExpensify Can I be added to Travel beta to test this one?

blazejkustra · 2025-02-03T17:17:00Z

FYI Eslint is failing @stitesExpensify

…rmatting

stitesExpensify · 2025-02-04T18:09:24Z

Whoops sorry about that. updated!

melvin-bot · 2025-02-06T01:48:38Z

@aldo-expensify Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

dominictb · 2025-02-06T01:53:17Z

+        return `${translateLocal('travel.departs')} ${format(date, 'EEEE, MMM d')} ${translateLocal('common.conjunctionAt')} ${format(date, 'HH:mm a')}`;
    }
-    return `${translateLocal('travel.departs')} ${format(date, 'EEEE, MMM d, yyyy')} ${translateLocal('common.conjunctionAt')} ${format(date, 'HH:MM')}`;
+    return `${translateLocal('travel.departs')} ${format(date, 'EEEE, MMM d, yyyy')} ${translateLocal('common.conjunctionAt')} ${format(date, 'HH:mm a')}`;


@aldo-expensify @stitesExpensify Hmm as we are adding AM/PM postfix here (a flag), I wonder if it's redundant to use 24-hour format (HH flag). So it could be something like 16:40 PM which is not standard to me.

Should it be 12-hour format only (hh)? That would align more to the current convention in App codebase (i.e. if we had a flag, we always used 12-hour format):

App/src/libs/DateUtils.ts

Line 485 in 40d29a0

return format(date, isFullFormat ? 'hh:mm:ss.SSS a' : 'hh:mm a');

App/src/libs/DateUtils.ts

Line 497 in 40d29a0

return format(date, 'yyyy-MM-dd hh:mm a');

App/src/libs/DateUtils.ts

Line 589 in 40d29a0

const tempTime = parse(updatedTime, 'hh:mm a', new Date());

App/src/libs/DateUtils.ts

Line 641 in 40d29a0

const parsedTime = parse(dateTime, isFullFormat ? 'hh:mm:ss.SSS a' : 'hh:mm a', new Date());

Yes I agree. I will fix that!

melvin-bot · 2025-02-06T16:29:50Z

@nkuoch Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

dominictb · 2025-02-06T17:52:05Z

@nkuoch We can merge now.

OSBotify · 2025-02-06T18:45:10Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2025-02-06T22:02:09Z

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 9.0.95-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	success ✅
🍎🔄 iOS HybridApp 🍎🔄	success ✅

github-actions · 2025-02-11T02:13:26Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.95-6 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌

stitesExpensify self-assigned this Jan 30, 2025

stitesExpensify requested review from a team as code owners January 30, 2025 23:30

This comment was marked as off-topic.

Sign in to view

melvin-bot Bot requested review from dominictb and sakluger January 30, 2025 23:30

Use minutes instead of months

40d29a0

roryabraham force-pushed the stites-fixDateFormatting branch from afc760e to 40d29a0 Compare January 31, 2025 00:05

blazejkustra approved these changes Jan 31, 2025

View reviewed changes

sakluger removed their request for review January 31, 2025 18:23

stitesExpensify added 2 commits January 31, 2025 13:29

Merge branch 'stites-fixDateFormatting' of github.com:Expensify/App i…

4771eee

…nto stites-fixDateFormatting

Merge branch 'main' of github.com:Expensify/App into stites-fixDateFo…

9bbd463

…rmatting

Merge branch 'main' of github.com:Expensify/App into stites-fixDateFo…

8dedb82

…rmatting

dominictb approved these changes Feb 6, 2025

View reviewed changes

melvin-bot Bot requested review from aldo-expensify and removed request for a team February 6, 2025 01:48

dominictb reviewed Feb 6, 2025

View reviewed changes

Fix capitalization

6fad659

dominictb approved these changes Feb 6, 2025

View reviewed changes

melvin-bot Bot requested a review from nkuoch February 6, 2025 16:29

nkuoch approved these changes Feb 6, 2025

View reviewed changes

aldo-expensify approved these changes Feb 6, 2025

View reviewed changes

aldo-expensify merged commit 50548f6 into main Feb 6, 2025

aldo-expensify deleted the stites-fixDateFormatting branch February 6, 2025 18:34

github-actions Bot mentioned this pull request Feb 6, 2025

Deploy Checklist: New Expensify 2025-02-06 #56482

Closed

melvin-bot Bot mentioned this pull request Feb 11, 2025

[$250] [Due for payment 2025-02-18] Departure time is wrong on trips in trip summary of trip room #56069

Closed

8 tasks

Conversation

stitesExpensify commented Jan 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

This comment was marked as off-topic.

melvin-bot Bot commented Jan 30, 2025

Uh oh!

OSBotify commented Jan 30, 2025

Uh oh!

stitesExpensify commented Jan 31, 2025

Uh oh!

sakluger commented Jan 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dominictb commented Feb 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

dominictb commented Feb 3, 2025

Uh oh!

blazejkustra commented Feb 3, 2025

Uh oh!

stitesExpensify commented Feb 4, 2025

Uh oh!

melvin-bot Bot commented Feb 6, 2025

Uh oh!

dominictb Feb 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aldo-expensify Feb 6, 2025

Choose a reason for hiding this comment

Uh oh!

stitesExpensify Feb 6, 2025

Choose a reason for hiding this comment

Uh oh!

stitesExpensify Feb 6, 2025

Choose a reason for hiding this comment

Uh oh!

melvin-bot Bot commented Feb 6, 2025

Uh oh!

dominictb commented Feb 6, 2025

Uh oh!

OSBotify commented Feb 6, 2025

Uh oh!

github-actions Bot commented Feb 6, 2025

Uh oh!

github-actions Bot commented Feb 11, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

stitesExpensify commented Jan 30, 2025 •

edited

Loading

sakluger commented Jan 31, 2025 •

edited

Loading

dominictb commented Feb 3, 2025 •

edited

Loading

dominictb Feb 6, 2025 •

edited

Loading