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

Polish for one-transaction view #39472

Merged
merged 26 commits into from
May 3, 2024
Merged

Polish for one-transaction view #39472

merged 26 commits into from
May 3, 2024

Conversation

NikkiWines
Copy link
Contributor

@NikkiWines NikkiWines commented Apr 3, 2024

Details

Follow up PR to #36934 to handle some bugs and edge cases.

Fixed Issues

$ #39512

Tests

  1. Log into an account that is a member of a workspace and make a single money request on the workspace chat
  2. Navigate to the workspace chat and click on the expense report preview
  3. Confirm that opens the report and that you see a combined expense view showing the details of both the expense report and transaction thread with an updated simplified icon (non-diagonal version) without a total.
  4. Modify some elements of the expense like the category, description, etc.
  5. Confirm that the last text of the report in the LHN updates appropriately
Screen.Recording.2024-04-05.at.15.59.47.mov
  1. Create another money request on the workspace chat
  2. Navigate back to the expense report and click into one of the transactions
  3. Add a comment or two on that transaction
  4. Go back to the report and delete the transaction that you had just commented on
  5. Confirm you do not see the combined one-transaction report view and instead see [Deleted Request] with some replies and the other transaction
  6. Click into the replies and confirm they load correctly
Screen.Recording.2024-04-05.at.16.01.14.mov
  1. Delete the other transaction on the report and confirm you still see the standard report view with [Deleted Request]
Screen.Recording.2024-04-05.at.16.01.48.mov
  • Verify that no errors appear in the JS console

Offline tests

N/A offline behavior not impacted

QA Steps

Same as test steps

  • 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 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-04-05.at.18.12.05.mov
iOS: Native
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-04-05.at.18.00.09.mp4
iOS: mWeb Safari
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-04-05.at.18.05.19.mp4
MacOS: Chrome / Safari
Screen.Recording.2024-04-05.at.15.59.47.mov
Screen.Recording.2024-04-05.at.16.01.14.mov
Screen.Recording.2024-04-05.at.16.01.48.mov
MacOS: Desktop
Screen.Recording.2024-04-05.at.16.26.31.mov
Screen.Recording.2024-04-05.at.16.27.10.mov

@NikkiWines NikkiWines self-assigned this Apr 3, 2024
@NikkiWines NikkiWines changed the title Fix reversed actions logic Polish for one-transaction view Apr 3, 2024
@NikkiWines NikkiWines marked this pull request as ready for review April 6, 2024 01:14
@NikkiWines NikkiWines requested a review from a team as a code owner April 6, 2024 01:14
@melvin-bot melvin-bot bot requested review from jayeshmangwani and removed request for a team April 6, 2024 01:14
Copy link

melvin-bot bot commented Apr 6, 2024

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

@jayeshmangwani
Copy link
Contributor

@allroundexperts, will you review this PR as you were the C+ for this PR , Or should I review it?
cc: @NikkiWines

@allroundexperts
Copy link
Contributor

I can review @jayeshmangwani

@NikkiWines NikkiWines requested review from allroundexperts and removed request for jayeshmangwani April 8, 2024 17:46
@NikkiWines
Copy link
Contributor Author

Friendly bump on this @allroundexperts 🙇

@allroundexperts
Copy link
Contributor

On it today!

@allroundexperts
Copy link
Contributor

Conflicts @NikkiWines

@NikkiWines
Copy link
Contributor Author

updated!

@allroundexperts
Copy link
Contributor

allroundexperts commented Apr 15, 2024

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 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
    • 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.js 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.
  • 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
Screen.Recording.2024-05-03.at.1.37.32.AM.mov
Android: mWeb Chrome
Screen.Recording.2024-05-03.at.1.33.20.AM.mov
iOS: Native
Screen.Recording.2024-05-03.at.1.32.44.AM.mov
iOS: mWeb Safari
Screen.Recording.2024-05-03.at.1.27.36.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2024-05-03.at.1.19.50.AM.mov
MacOS: Desktop
Screen.Recording.2024-05-03.at.1.25.49.AM.mov

@NikkiWines
Copy link
Contributor Author

I'm still unable to reproduce that currency / report total issue, but it's also been brought up before this PR here. So, @allroundexperts let's move forward with this as it is and

@NikkiWines
Copy link
Contributor Author

@allroundexperts friendly bump 🙇

@NikkiWines
Copy link
Contributor Author

Bumped in slack here

@allroundexperts
Copy link
Contributor

Hi @NikkiWines!

The LHN is not reflecting correctly if the report has been submitted or not in offline mode.

Screen.Recording.2024-04-29.at.1.50.19.AM.mov

@NikkiWines
Copy link
Contributor Author

@allroundexperts I can reproduce that bug but it doesn't seem specific to the one-transaction report view, so let's not hold this PR on that change 🙇

Screen.Recording.2024-04-30.at.16.36.30.mov

@NikkiWines
Copy link
Contributor Author

@allroundexperts friendly bump 🙇

Copy link
Contributor

@allroundexperts allroundexperts left a comment

Choose a reason for hiding this comment

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

Looking good!

@melvin-bot melvin-bot bot requested a review from amyevans May 2, 2024 21:03
Copy link

melvin-bot bot commented May 2, 2024

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

amyevans
amyevans previously approved these changes May 3, 2024
Copy link
Contributor

@amyevans amyevans left a comment

Choose a reason for hiding this comment

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

LGTM! Just one NAB, feel free to merge

src/libs/ReportActionsUtils.ts Outdated Show resolved Hide resolved
Co-authored-by: Amy Evans <amy@expensify.com>
@NikkiWines NikkiWines requested a review from amyevans May 3, 2024 16:46
Copy link
Contributor

@amyevans amyevans left a comment

Choose a reason for hiding this comment

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

Nice!

@amyevans amyevans merged commit 1fc0339 into main May 3, 2024
15 checks passed
@amyevans amyevans deleted the nikki-load-oldest-actions branch May 3, 2024 20:32
@OSBotify
Copy link
Contributor

OSBotify commented May 3, 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.

@kbecciv
Copy link

kbecciv commented May 7, 2024

This PR is failing because of issue #39450

The issue is reproducible in: All Platforms, didn't verify on mWeb yet.

1715081459641.39472_web.mp4
1715086381124.Screen_Recording_2024-05-07_at_3.52.18_PM.1.mov
1715081699781.39472_Android.mp4
1715081945664.39472_iOS.mp4

@NikkiWines
Copy link
Contributor Author

Weird, that's one of the things I tested it on right before merging. I'll look into fixing it but since it's the same behavior as before it's not a blocker 👍

@OSBotify
Copy link
Contributor

OSBotify commented May 9, 2024

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.71-6 🚀

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

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

Successfully merging this pull request may close these issues.

6 participants