Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable/disable per diem rates #51232

Merged
merged 29 commits into from
Nov 7, 2024
Merged

Conversation

shubham1206agra
Copy link
Contributor

@shubham1206agra shubham1206agra commented Oct 22, 2024

Details

Fixed Issues

$ #50862

Tests

Pre-requisite
Make sure you are on newDotPerDiem beta before testing this feature.

  1. Go to the workspace where you want to enable per diem feature.
  2. Go to More Features.
  3. Toggle the Per diem under spend to enable/disable the feature.
  4. Make sure that if you are on paid workspace, it is asking you to upgrade the workspace.
  5. Make sure you can go to the per diem page.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

Same as Tests

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 verified the translation was requested/reviewed 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.js 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.
  • 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
Screen.Recording.2024-10-31.at.8.36.18.AM.mov
iOS: Native
Screen.Recording.2024-10-31.at.10.15.02.AM.mov
iOS: mWeb Safari
Screen.Recording.2024-10-30.at.10.01.55.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2024-10-30.at.9.29.46.PM.mov
MacOS: Desktop
Screen.Recording.2024-10-31.at.9.57.50.AM.mov

@shubham1206agra
Copy link
Contributor Author

@Gonals I am almost done with this PR.

@c3024
Copy link
Contributor

c3024 commented Oct 24, 2024

@shubham1206agra

Can you please share the extract of the design doc?

@shubham1206agra
Copy link
Contributor Author

@Gonals Can you share doc with @c3024?

@Gonals
Copy link
Contributor

Gonals commented Oct 24, 2024

Shared

@shubham1206agra shubham1206agra marked this pull request as ready for review October 31, 2024 04:47
@shubham1206agra shubham1206agra requested review from a team as code owners October 31, 2024 04:47
@melvin-bot melvin-bot bot requested review from jjcoffee and removed request for a team October 31, 2024 04:47
@shubham1206agra
Copy link
Contributor Author

@c3024 Please proceed with the checklist.

@shubham1206agra
Copy link
Contributor Author

@shawnborton
Copy link
Contributor

cc @bfitzexpensify - what's the correct help article URL for this?

@bfitzexpensify
Copy link
Contributor

@shawnborton
Copy link
Contributor

Do we have one ready for NewDot though? Also, where is this link shown exactly @shubham1206agra ?

@bfitzexpensify
Copy link
Contributor

Sorry, completely missed the ND portion, need to have my coffee.

We don't have ND help docs up yet - opened https://github.com/Expensify/Expensify/issues/442420 to get them sorted, should take me a day or two.

We don't need that to be a blocker for this, I can open a PR to update the link once the help docs are ready.

@c3024
Copy link
Contributor

c3024 commented Nov 7, 2024

@bfitzexpensify

need to have my coffee.

This PR has other things apart from the link. I think this PR should not be closed.

@shubham1206agra
Copy link
Contributor Author

Do we have one ready for NewDot though? Also, where is this link shown exactly @shubham1206agra ?

In OldDot, in PerDiem section.

@bfitzexpensify bfitzexpensify reopened this Nov 7, 2024
@shubham1206agra
Copy link
Contributor Author

@c3024 Can you finish the review now?

title: 'Per diem',
description:
'Per diem is a great way to keep your daily costs compliant and predictable whenever your employees travel. Enjoy features like custom rates, default categories, and more granular details like destinations and subrates.',
onlyAvailableOnPlan: 'Per diem are only available on the Control plan, starting at ',
Copy link
Contributor

@c3024 c3024 Nov 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
onlyAvailableOnPlan: 'Per diem are only available on the Control plan, starting at ',
onlyAvailableOnPlan: 'Per diem is only available on the Control plan, starting at ',

NIT: Google says plural for per diem is per diems.

So, it might need to be confirmed if this should be "Per diems are" or "Per diem is" or retain as it is.

Copy link
Contributor

@c3024 c3024 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested the enabling/disabling and view of the per diem page. LGTM!

@melvin-bot melvin-bot bot requested a review from Gonals November 7, 2024 08:52
@Gonals
Copy link
Contributor

Gonals commented Nov 7, 2024

Neat! Let's merge! We can update the help later. This is behind a beta, anyways. @shubham1206agra, send the PRs with the rest of the functionality (importing/exporting/setting default category) my way when they are ready. I'll test with the backend and deploy the backend PRs accordingly

@Gonals Gonals merged commit e000d80 into Expensify:main Nov 7, 2024
21 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Nov 7, 2024

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

Copy link
Contributor

github-actions bot commented Nov 7, 2024

🚀 Deployed to staging by https://github.com/Gonals in version: 9.0.59-0 🚀

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

Copy link
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.59-3 🚀

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

@@ -76,9 +80,12 @@ function WorkspaceUpgradePage({route}: WorkspaceUpgradePageProps) {
case CONST.UPGRADE_FEATURE_INTRO_MAPPING.companyCards.id:
Policy.enableCompanyCards(policyID, true);
break;
case CONST.UPGRADE_FEATURE_INTRO_MAPPING.perDiem.id:
PerDiem.enablePerDiem(policyID, true, perDiemCustomUnit?.customUnitID);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coming from #52201.
enablePerDiem needs a parameter to disable redirection, because there is a link on this page to view the subscription page, and when we tap it, this function will also be called. In such cases, we need to disable redirection. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants