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

Add merchant and date fields to manual requests #23648

Conversation

lukemorawski
Copy link
Contributor

@lukemorawski lukemorawski commented Jul 26, 2023

Details

We want to add new fields to the money request page - merchant and date.
Those new fields need to be hidden under the “Show more” button. Button disappears when the details are shown.
Values of those fields are taken from the “iou” object created when creating a new money request.

Fixed Issues

$ #23245
PROPOSAL:
We need to add a simple bool state flag to the MoneyRequestConfirmationList.js and a small button with horizontal line that will toggle this flag. The flag will control the visibility of two new MenuItemWithTopDescription components.
New props would need to be introduced to the MoneyRequestConfirmationList component - one for passing the date and the other to pass the merchant value.
Those props are passed from the MoneyRequestConfirmPage component, and are taken from an Onyx subscription to ‘iou’ object
In order get the new default values in the ‘iou’ object we need to add them to the object merged in resetMoneyRequestInfo function from IOU.js. Default value for merchant is an empty string and date is current date.
In future PRs those values will be editable.

desktop.chrome.mov

Tests

  • Open app

  • log in

  • click on the FAB + button on the main screen

  • select Request Money

  • fill out details and reach the Details screen

  • Verify that no errors appear in the JS console

Offline tests

QA 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 / Chrome
    • iOS / native
    • iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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 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
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web desktop chrome
Mobile Web - Chrome android chrome
Mobile Web - Safari ios web
Desktop dekstop native
iOS ios native
Android android native

@lukemorawski lukemorawski requested a review from a team as a code owner July 26, 2023 14:05
@melvin-bot melvin-bot bot requested review from 0xmiros and shawnborton and removed request for a team July 26, 2023 14:05
@melvin-bot
Copy link

melvin-bot bot commented Jul 26, 2023

@shawnborton @0xmiroslav 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]

@Beamanator
Copy link
Contributor

@lukemorawski thanks for the PR!! Looks like there's at least 1 file with a conflict :D

@0xmiroslav can you please put this relatively high on your priority list? We would love to get this in the App soon, as a few other issues are waiting for it 👍

@lukemorawski
Copy link
Contributor Author

conflict resolved

onPress={toggleShowAllFields}
text={showAllFields ? translate('common.showLess') : translate('common.showMore')}
shouldShowRightIcon
iconRight={showAllFields ? Expensicons.UpArrow : Expensicons.DownArrow}
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we make the icon use our standard colors.icon color?

Copy link
Contributor

Choose a reason for hiding this comment

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

This can be a global change for all default buttons too

@shawnborton
Copy link
Contributor

Looks good so far, curious to see this on desktop too.

Is there ever a situation where a "Show less" button appears?

@lukemorawski
Copy link
Contributor Author

@shawnborton Ah no, forgot to remove that show less thing :) Will do that in a mo.

@lukemorawski
Copy link
Contributor Author

@shawnborton sorry, but I couldn't find an example in the app where an button icon is stylised with the colour you mention. Can you point to a place in the app where this colour is used?

@lukemorawski
Copy link
Contributor Author

Ok, I think I got it

@Beamanator
Copy link
Contributor

@0xmiroslav can you please test this on all platforms today? If not, can you let me know so I can find a new C+ who is available?

@situchan
Copy link
Contributor

I am available to review right now

@Beamanator
Copy link
Contributor

Ping'd you both in slack 👍

@Beamanator Beamanator requested review from situchan and removed request for 0xmiros July 28, 2023 07:21
@Beamanator
Copy link
Contributor

@situchan you're up! Please review! And thanks for being available quickly 🙏

Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

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

Let's make this PR simple by undoing any unnecessary changes.

Comment on lines 103 to 121
...(isNewChatReport ? {pendingFields: {createChat: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD}} : {}),
...(isNewChatReport
? {
pendingFields: {
createChat: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
},
}
: {}),
Copy link
Contributor

Choose a reason for hiding this comment

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

Please revert any unnecessary changes like this as long as they don't break lint.

Comment on lines 131 to 137
...(isNewIOUReport
? {
pendingFields: {
createChat: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
},
}
: {}),
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

@@ -336,7 +361,6 @@ function requestMoney(report, amount, currency, payeeEmail, payeeAccountID, part
if (iouReport) {
if (isPolicyExpenseChat) {
iouReport = {...iouReport};

Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

Copy link
Contributor

Choose a reason for hiding this comment

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

this is not undo'ed yet

Comment on lines 500 to 528
...(existingGroupChatReport ? {} : {[groupCreatedReportAction.reportActionID]: groupCreatedReportAction}),
...(existingGroupChatReport
? {}
: {
[groupCreatedReportAction.reportActionID]: groupCreatedReportAction,
}),
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

? {}
: {
[groupCreatedReportAction.reportActionID]: {pendingAction: null},
}),
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

Comment on lines 1342 to 1346
API.write('SendMoneyWithWallet', params, {
optimisticData,
successData,
failureData,
});
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

Comment on lines 1364 to 1368
API.write('SendMoneyViaPaypal', params, {
optimisticData,
successData,
failureData,
});
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

Copy link
Contributor

Choose a reason for hiding this comment

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

this is not undo'ed yet

Comment on lines 1444 to 1446
Onyx.merge(ONYXKEYS.IOU, {
participants,
});
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

Comment on lines 1397 to 1464
splitBill,
splitBillAndOpenReport,
payMoneyRequest,
requestMoney,
resetMoneyRequestInfo,
sendMoneyElsewhere,
sendMoneyViaPaypal,
payMoneyRequest,
sendMoneyWithWallet,
startMoneyRequest,
resetMoneyRequestInfo,
setMoneyRequestId,
setMoneyRequestAmount,
setMoneyRequestCurrency,
setMoneyRequestDescription,
setMoneyRequestId,
setMoneyRequestParticipants,
splitBill,
splitBillAndOpenReport,
startMoneyRequest,
Copy link
Contributor

Choose a reason for hiding this comment

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

please keep original orders so I can see clearly what are removed and what are newly added

@@ -1,4 +1,4 @@
import React, {useCallback, useEffect, useRef, useMemo} from 'react';
import React, {useCallback, useEffect, useMemo, useRef} from 'react';
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

@situchan
Copy link
Contributor

situchan commented Aug 1, 2023

@lukemorawski please re-request review from me when ready. Thanks

@lukemorawski lukemorawski requested a review from situchan August 2, 2023 07:14
@Beamanator
Copy link
Contributor

Code is looking great!! I still see a few places changes that weren't necessary (reordering the withCurrentPersonalDetails prop types & default prop types, but for the sake of urgency @situchan please review as is 🙏 we really need to get this merged soon 🙏

Also FYI @lukemorawski I'm going to remove Lukemorawski 23245 from the PR title if you don't mind 😅

@lukemorawski
Copy link
Contributor Author

@Beamanator hey, yeah no worries, remove the name 😃

@Beamanator Beamanator changed the title Lukemorawski 23245 add merchant and date fields to manual requests Add merchant and date fields to manual requests Aug 2, 2023
@Beamanator
Copy link
Contributor

Done! 😅 👍

Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

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

Looks good, minor feedback

@@ -103,6 +113,9 @@ function MoneyRequestConfirmationList(props) {
// Prop functions pass props itself as a "this" value to the function which means they change every time props change.
const {translate, onSendMoney, onConfirm, onSelectParticipant} = props;

// A flag and a toggler for showing the rest of the form fields
const [showAllFields, toggleShowAllFields] = useReducer((state) => !state, false);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not useState here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I like this approach as it exposes a bool flag and a toggle function in one line. With useState you have declare a separate function to toggle the flag. Nice and clean.

@@ -148,6 +148,8 @@ export default {
someone: 'Alguien',
total: 'Total',
edit: 'Editar',
showMore: 'Mostrar más',
merchant: 'comerciante',
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this correct? Just asking because first letter is not capitalized like English

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, should be capitalized.

@situchan
Copy link
Contributor

situchan commented Aug 2, 2023

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 / Chrome
    • iOS / native
    • iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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(themeColors.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 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

Web
web.mov
Mobile Web - Chrome
mchrome.mov
Mobile Web - Safari
msafari.mov
Desktop
desktop.mov
iOS
ios.mov
Android android

@Beamanator
Copy link
Contributor

Oof, @lukemorawski can you please fix the conflicts & respond to @situchan 's comments?

Then @situchan can you please do a re-review after conflicts are fixed to make sure nothing's broken?

Anything keeping us from getting this merged today, y'all??

@lukemorawski lukemorawski requested a review from situchan August 3, 2023 08:29
Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

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

Re-tested latest code. Confirmed nothing broken

Copy link
Contributor

@Beamanator Beamanator left a comment

Choose a reason for hiding this comment

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

Thanks so much gents, let's merge!

@Beamanator Beamanator merged commit e26d900 into Expensify:main Aug 3, 2023
@OSBotify
Copy link
Contributor

OSBotify commented Aug 3, 2023

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

@OSBotify
Copy link
Contributor

OSBotify commented Aug 3, 2023

🚀 Deployed to staging by https://github.com/Beamanator in version: 1.3.50-0 🚀

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

@mvtglobally
Copy link

@lukemorawski @shawnborton @Beamanator
Can you please confirm for QA what do we need to verify on the Details screen after reaching it?

@Beamanator
Copy link
Contributor

Yes @mvtglobally - sorry we missed that, but I tested in staging and it's working well! 👍

@dylanexpensify
Copy link
Contributor

@Beamanator just to confirm, did this get deployed/we can close #295259 now?

@Beamanator
Copy link
Contributor

@dylanexpensify technically we can probably close the internal issue, BUT we won't close the App one yet since we have to pay out the C+ here once it's on prod for 7 days

And also, this PR is only on staging for today, we're currently not planning to deploy today so won't get to prod till next week

@dylanexpensify
Copy link
Contributor

Ahh nice nice, ok let's leave open until at prod! TY! <3

@OSBotify
Copy link
Contributor

OSBotify commented Aug 7, 2023

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Aug 7, 2023

🚀 Deployed to staging by https://github.com/Beamanator in version: 1.3.51-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Aug 9, 2023

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.51-2 🚀

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.

7 participants