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.

Sign up for GitHub

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

Jump to bottom

feat: skip participant step in create flow #56090

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
Open

feat: skip participant step in create flow #56090

wants to merge 12 commits into from
+115 −42

Conversation

nkdengineer
Copy link
Contributor

Explanation of Change

feat: skip participant step in create flow

Fixed Issues

$ #55717
PROPOSAL: #55717 (comment)

Tests

Precondition: The account has the default workspace is a group workspace

  1. From global FAB > Create expense
  2. For each flow Manual/Scan/Distance
  3. Verify that the default workspace is auto-assigned as participant after we pass the first step
  • Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

Precondition: The account has the default workspace is group workspace

  1. From global FAB > Create expense
  2. For each flow Manual/Scan/Distance
  3. Verify that the default workspace is auto assigned as participant after we pass the first step
  • 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
Screen.Recording.2025-01-30.at.23.07.08.mov
Android: mWeb Chrome
Screen.Recording.2025-01-30.at.23.01.16.mov
iOS: Native
Screen.Recording.2025-01-30.at.23.20.26.mov
iOS: mWeb Safari
Screen.Recording.2025-01-30.at.23.03.06.mov
MacOS: Chrome / Safari
Screen.Recording.2025-01-30.at.22.59.37.mov
MacOS: Desktop
Screen.Recording.2025-01-30.at.23.23.07.mov

@nkdengineer nkdengineer marked this pull request as ready for review January 30, 2025 16:45
@nkdengineer nkdengineer requested a review from a team as a code owner January 30, 2025 16:45
@melvin-bot melvin-bot bot requested a review from mollfpr January 30, 2025 16:45
@melvin-bot Melvin Bot
Copy link

melvin-bot bot commented Jan 30, 2025

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

@melvin-bot melvin-bot bot removed the request for review from a team January 30, 2025 16:45
@trjExpensify
Copy link
Contributor

👋 @mollfpr are you going to be able to review this (your) today!?

@github-actions GitHub Actions
Copy link
Contributor

🚧 @trjExpensify has triggered a test build. You can view the workflow run here.

@github-actions GitHub Actions

This comment has been minimized.

Sign in to view
@mollfpr
Copy link
Contributor

mollfpr commented Jan 31, 2025

@trjExpensify Yup!

@trjExpensify
Copy link
Contributor

@nkdengineer you're missing the right caret:

image image

mollfpr
mollfpr reviewed Jan 31, 2025
View reviewed changes
Copy link
Contributor

@mollfpr mollfpr left a comment

Choose a reason for hiding this comment

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

The test looks good, except the missing caret icon on the participant select. Also, I leave comments for clarification.

src/pages/iou/request/step/IOURequestStepAmount.tsx Outdated Show resolved Hide resolved
src/pages/iou/request/step/IOURequestStepScan/index.tsx Show resolved Hide resolved
@nkdengineer
Copy link
Contributor Author

@mollfpr Updated with right icon. Please help to check again.

@nkdengineer
Copy link
Contributor Author

@mollfpr I updated, please help to check again.

@shawnborton
Copy link
Contributor

Will run a test build on this one too.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 6, 2025

🚧 @shawnborton has triggered a test build. You can view the workflow run here.

mollfpr
mollfpr reviewed Feb 6, 2025
View reviewed changes
Copy link
Contributor

@mollfpr mollfpr left a comment

Choose a reason for hiding this comment

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

The changes look good! @nkdengineer Could you resolve the issue on lint and test unit? Thanks!

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 6, 2025

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/56090/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/56090/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/56090/NewExpensify.dmg https://56090.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@dannymcclain
Copy link
Contributor

Feeling really good to me!

@shawnborton
Copy link
Contributor

I don't think we want this for Invoices, otherwise you kinda end up sending the Invoice to yourself right?
CleanShot 2025-02-06 at 14 57 47@2x

@dubielzyk-expensify
Copy link
Contributor

Other than what Shawn is mentioning it's feeling pretty great to me too 👍

@trjExpensify
Copy link
Contributor

I don't think we want this for Invoices, otherwise you kinda end up sending the Invoice to yourself right?

Agreed, this was only intended for the Create expense flow not the `Send invoice flow. 👍

@nkdengineer
Copy link
Contributor Author

Agreed, this was only intended for the Create expense flow not the `Send invoice flow. 👍

I fixed this bug.

@nkdengineer
Copy link
Contributor Author

The changes look good! @nkdengineer Could you resolve the issue on lint and test unit? Thanks!

@mollfpr Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@shawnborton shawnborton shawnborton left review comments

@dannymcclain dannymcclain dannymcclain left review comments

@trjExpensify trjExpensify trjExpensify left review comments

@mollfpr mollfpr mollfpr left review comments

At least 1 approving review is required to merge this pull request.

Assignees

@nkdengineer nkdengineer

Labels
Ready To Build
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@nkdengineer @trjExpensify @mollfpr @shawnborton @dannymcclain @dubielzyk-expensify