Correct per diem time calculation for same-day expenses #56295

Shahidullah-Muffakir · 2025-02-04T04:26:25Z

Explanation of Change

For per diem expenses, if the start and end dates are the same, show only the first day's hours and skip trip days and last day hours.

Fixed Issues

$ #55449
PROPOSAL: #55449 (comment)

Tests

Precondition:

Workspace has per diem rates (we can add these Per diem rates in OD)

Steps:

Go to staging.new.expensify.com → Workspace Chat
Click + > Submit expense > Per diem
Select a destination → Next
Set time: Start: 8:00 AM, End: 10:00 AM (same day)
Complete the steps → Confirmation Page
Verify that:
- First Day: 2.00 hours
- Trip Days / Last Day: Not shown
Verify that "Trip Days" and "Last Day" are not shown for same-day expenses
Submit a multi-day per diem expense and ensure the trip days and last day are calculated correctly

Verify that no errors appear in the JS console

Offline tests

Same as tests.

QA Steps

Precondition:

Workspace has per diem rates (we can add these Per diem rates in OD)

Steps:

Go to staging.new.expensify.com → Workspace Chat
Click + > Submit expense > Per diem
Select a destination → Next
Set time: Start: 8:00 AM, End: 10:00 AM (same day)
Complete the steps → Confirmation Page
Verify that:
- First Day: 2.00 hours
- Trip Days / Last Day: Not shown
Verify that "Trip Days" and "Last Day" are not shown for same-day expenses
Submit a multi-day per diem expense and ensure the trip days and last day are calculated correctly

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2025-02-04.at.9.04.11.AM.mov

Android: mWeb Chrome

android.20web-3.mp4

iOS: Native

ios.native.mov

iOS: mWeb Safari

ios.safari.mov

MacOS: Chrome / Safari

macos.20web.mp4

MacOS: Desktop

ios.20desktop-2.mp4

melvin-bot · 2025-02-04T04:26:30Z

@c3024 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]

c3024 · 2025-02-04T07:06:20Z

src/libs/PerDiemRequestUtils.ts

@@ -258,6 +258,19 @@ function getTimeDifferenceIntervals(transaction: OnyxEntry<Transaction>) {
    const customUnitRateDate = transaction?.comment?.customUnit?.attributes?.dates ?? {start: '', end: ''};
    const startDate = new Date(customUnitRateDate.start);
    const endDate = new Date(customUnitRateDate.end);
+    // Check if start and end dates are on the same day
+    const isSameDay = startOfDay(startDate).getTime() === startOfDay(endDate).getTime();


Let us use the isSameDay of date-fns to avoid any unexpected edge cases.

Can you please remove the comments too? The code looks self-explanatory.

Thanks for the review, Updated.

c3024 · 2025-02-04T07:48:54Z

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

c3024 · 2025-02-04T07:50:14Z

@Shahidullah-Muffakir

Please add a unit test for the same day case.

Correct per diem time calculation for same-day expenses

d6f8626

Shahidullah-Muffakir requested a review from a team as a code owner February 4, 2025 04:26

melvin-bot bot requested review from c3024 and removed request for a team February 4, 2025 04:26

Shahidullah-Muffakir mentioned this pull request Feb 4, 2025

[$250] Per diem - Time summary on the confirmation page is incorrect #55449

Open

8 tasks

c3024 suggested changes Feb 4, 2025

View reviewed changes

use isSameDay for finding the same day

b013290

Shahidullah-Muffakir added 2 commits February 4, 2025 14:19

add unit test for getTimeDifferenceIntervals

18ddc74

fix lint

40f1c51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Correct per diem time calculation for same-day expenses #56295

Correct per diem time calculation for same-day expenses #56295

Shahidullah-Muffakir commented Feb 4, 2025

melvin-bot bot commented Feb 4, 2025

c3024 Feb 4, 2025

Shahidullah-Muffakir Feb 4, 2025 •

edited

Loading

c3024 commented Feb 4, 2025 •

edited

Loading

c3024 commented Feb 4, 2025

Correct per diem time calculation for same-day expenses #56295

Are you sure you want to change the base?

Correct per diem time calculation for same-day expenses #56295

Conversation

Shahidullah-Muffakir commented Feb 4, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Feb 4, 2025

c3024 Feb 4, 2025

Choose a reason for hiding this comment

Shahidullah-Muffakir Feb 4, 2025 • edited Loading

Choose a reason for hiding this comment

c3024 commented Feb 4, 2025 • edited Loading

Reviewer Checklist

Screenshots/Videos

c3024 commented Feb 4, 2025

Shahidullah-Muffakir Feb 4, 2025 •

edited

Loading

c3024 commented Feb 4, 2025 •

edited

Loading