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

Refactor/23149 money request page #23979

Merged
merged 39 commits into from
Aug 4, 2023

Conversation

koko57
Copy link
Contributor

@koko57 koko57 commented Aug 1, 2023

Details

Fixed Issues

$ #23149
PROPOSAL: #23149(comment)

Tests

  1. Start an IOU flow (request money, split bill)
  2. Verify that the value is stored properly, the whole flow works as expected and there is no other errors
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

  1. Start an IOU flow (request money, split bill)
  2. Verify that the value is stored properly, the whole flow works as expected and there is no other errors
  • 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 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
    • 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
Screen.Recording.2023-08-01.at.09.42.00.mp4
Mobile Web - Chrome
Screen.Recording.2023-08-01.at.11.53.10.mp4
Mobile Web - Safari
iphone_safari.mov
Desktop
Screen.Recording.2023-08-01.at.11.54.47.mp4
iOS
iphone_app.mov
Android
Screen.Recording.2023-08-01.at.11.41.32.mp4

@melvin-bot
Copy link

melvin-bot bot commented Aug 1, 2023

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

src/libs/MoneyRequestUtils.js Outdated Show resolved Hide resolved
src/pages/iou/steps/MoneyRequestAmountForm.js Outdated Show resolved Hide resolved
src/pages/iou/steps/MoneyRequestAmountForm.js Show resolved Hide resolved
@mountiny
Copy link
Contributor

mountiny commented Aug 1, 2023

@koko57 Thanks for pushing this ahead. You can now merge main, the RNAnimated has been updated in main

@s77rt
Copy link
Contributor

s77rt commented Aug 1, 2023

Taking this.

@s77rt s77rt mentioned this pull request Aug 1, 2023
56 tasks
@koko57
Copy link
Contributor Author

koko57 commented Aug 1, 2023

@s77rt @mountiny just found one bug myself, fixing it please hold on with tests until I push the fix 🙂 thanks!

@mountiny mountiny requested a review from s77rt August 1, 2023 10:39
@koko57
Copy link
Contributor Author

koko57 commented Aug 4, 2023

@marcaaron thanks for the review! 😊 I fixed all the code with comments without NAB label.

@koko57
Copy link
Contributor Author

koko57 commented Aug 4, 2023

@marcaaron @mountiny Can I start working on this followup PR?

@marcaaron marcaaron self-requested a review August 4, 2023 20:48
Copy link
Contributor

@marcaaron marcaaron left a comment

Choose a reason for hiding this comment

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

Thanks for the changes. 👍 from me.

@marcaaron marcaaron merged commit 5f0a741 into Expensify:main Aug 4, 2023
@marcaaron
Copy link
Contributor

@koko57 I'd say go for it unless @mountiny wants to hold off for his next round of changes (maybe this is easier for everyone).

@OSBotify
Copy link
Contributor

OSBotify commented Aug 4, 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.

@mountiny
Copy link
Contributor

mountiny commented Aug 6, 2023

@koko57 Yes please, thanks everyone for pushing this ahead, no need to wait with the follow ups

@OSBotify
Copy link
Contributor

OSBotify commented Aug 7, 2023

🚀 Deployed to staging by https://github.com/marcaaron 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 ✅

@OSBotify
Copy link
Contributor

OSBotify commented Aug 9, 2023

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.52-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Aug 9, 2023

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.52-0 🚀

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

@koko57 koko57 mentioned this pull request Aug 9, 2023
59 tasks
@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.52-5 🚀

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

}
setCurrentAmount((prevAmount) => {
setSelection((prevSelection) => getNewSelection(prevSelection, prevAmount.length, newAmountWithoutSpaces.length));
return MoneyRequestUtils.stripCommaFromAmount(newAmountWithoutSpaces);
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 #23933

Cursor jumps to next position when we use ',' in request money when language is English

This happens because we were updating the cursor position using the non-comma stripped amount and only after that strip the comma from the amount.
We resolved this by stripping comma from the amount first and updating the selection after that, i.e

  setCurrentAmount((prevAmount) => {
      const strippedAmount = MoneyRequestUtils.stripCommaFromAmount(newAmountWithoutSpaces);
      setSelection((prevSelection) => getNewSelection(prevSelection, prevAmount.length, strippedAmount.length));
      return strippedAmount;
  });

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that makes sense but it's not a regression from this PR. That logic was copied from src/pages/iou/steps/MoneyRequestAmount.js,

@sobitneupane
Copy link
Contributor

This issue was caused by change introduced by this PR.

Issue: Web - App crashes when currency in url is changed to invalid currency code

Steps for reproduction:

  1. Go to any chat
  2. Open request money
  3. Change currency in currency list
  4. Notice there is a currency code in url indicating selected currency
  5. (a). Now change that currency code in url to invalid currency code for example ABCD
    (b). Change currency code in url to not invalid currency code but keep it 3 letters like ABC

@koko57
Copy link
Contributor Author

koko57 commented Oct 9, 2023

@sobitneupane I don't think this PR introduced the issue 🙂 We didn't validate the currency before these changes were introduced
Screenshot 2023-10-09 at 10 03 17


useFocusEffect(
useCallback(() => {
focusTextInput();
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 #22388, this has caused a small regression
We're focusing the input immediately after the page is focused. When this happens when the page starts navigating, it will cancel the transition animation and we just see an abrupt page change

It was later decided to use this solution whenever we need to autofocus a TexInput, which doesn't have this problem

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@eVoloshchak It was already implemented earlier

useFocusEffect(
useCallback(() => {
focusTextInput();
}, []),
);
. It was just moved to the new file 🙂

Copy link
Contributor

Choose a reason for hiding this comment

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

Oops, I see, thank you!

) : null}
<Button
success
style={[styles.w100, styles.mt5]}
Copy link
Contributor

Choose a reason for hiding this comment

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

Adding a mt5 here caused this issue.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it wasn't added in this commit 😅 it was just moved from the old file without changes

style={[styles.w100, styles.mt5]}


const iouType = lodashGet(route, 'params.iouType', '');
const reportID = lodashGet(route, 'params.reportID', '');
const isEditing = lodashGet(route, 'path', '').includes('amount');
Copy link
Contributor

@0xmiros 0xmiros Dec 1, 2023

Choose a reason for hiding this comment

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

This didn't work when open deep link from chat message.
More details about the root cause: #26471 (comment)

So we update logic like this:

Suggested change
const isEditing = lodashGet(route, 'path', '').includes('amount');
const isEditing = Navigation.getActiveRoute().includes('amount');

EDIT: the original logic was added here: https://github.com/Expensify/App/pull/17964/files#diff-879f243892ee617d3ea9bc2550496a07521c2b91d2bec3eb12b90f09aac6a05aR94

}, [onSubmitButtonPress, currentAmount]);

const formattedAmount = MoneyRequestUtils.replaceAllDigits(currentAmount, toLocaleDigit);
const buttonText = isEditing ? translate('common.save') : translate('common.next');
Copy link
Contributor

Choose a reason for hiding this comment

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

This component is used in EditRequestAmountPage as well. isEditing prop is not passed so it caused #33011

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@situchan this prop was passed properly in EditRequestAmountPage, but it was lost during refactor https://github.com/Expensify/App/pull/28618/files#diff-598c08eb72e9071a7ab827304a24f3dd0a769b65f71e9c30140df3eda8c4b667

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.