[Internal QA]: Add amex custom feed new option #52890

narefyev91 · 2024-11-21T11:53:22Z

Explanation of Change

Polish updates to Amex card flow

Fixed Issues

$ #52798
PROPOSAL:

Tests

Start adding new feed
Choose Amex card
Verify that 3 options are available now
Click on Personal -> Verify that bank account connection is started

Verify that no errors appear in the JS console

Offline tests

No changes

QA Steps

Start adding new feed
Choose Amex card
Verify that 3 options are available now
Click on Personal -> Verify that bank account connection is started

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.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

android1.mp4

Android: mWeb Chrome

android-web1.mp4

iOS: Native

ios1.mp4

iOS: mWeb Safari

ios-web1.mp4

MacOS: Chrome / Safari

web1.mp4

MacOS: Desktop

desktop1.mp4

melvin-bot · 2024-11-21T11:53:28Z

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

allgandalf · 2024-11-21T12:13:31Z

src/languages/es.ts

@@ -3268,6 +3268,7 @@ const translations = {
                },
                amexCorporate: 'Seleccione esto si el frente de sus tarjetas dice “Corporativa”',
                amexBusiness: 'Seleccione esta opción si el frente de sus tarjetas dice “Negocios”',
+                amexPersonal: 'Seleccione esta opción si sus tarjetas son personales.',


@narefyev91 were these translations confirmed?

@allgandalf used copilot :-)

JamesGPT gave me:

Selecciona esta opción si tus tarjetas son personales.

Let's confirm this before moving forward

asked on slack for help

allgandalf · 2024-11-21T12:14:34Z

src/pages/workspace/companyCards/addNew/AmexCustomFeed.tsx

+        {
+            value: CONST.COMPANY_CARDS.AMEX_CUSTOM_FEED.PERSONAL,
+            text: CONST.COMPANY_CARDS.AMEX_CUSTOM_FEED.PERSONAL,
+            alternateText: translate('workspace.companyCards.addNewCard.amexPersonal'),


@mountiny is PERSONAL card already supported with the API on the BE

src/languages/en.ts

src/languages/es.ts

Co-authored-by: Gandalf <[email protected]>

allgandalf · 2024-11-21T13:08:24Z

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 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-11-21.at.7.04.58.PM.mov

Android: mWeb Chrome

Screen.Recording.2024-11-21.at.7.06.16.PM.mov

iOS: Native

Screen.Recording.2024-11-21.at.7.00.29.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-11-21.at.7.01.22.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-11-21.at.6.57.54.PM.mov

MacOS: Desktop

Screen.Recording.2024-11-21.at.7.09.23.PM.mov

allgandalf

This looks great, thanks for the quick work @narefyev91 🙇

OSBotify · 2024-11-21T18:16:09Z

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

github-actions · 2024-11-22T20:32:45Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.66-0 🚀

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

joekaufmanexpensify · 2024-11-25T16:07:49Z

Tested and passed!

github-actions · 2024-11-26T16:14:10Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.66-8 🚀

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

Add amex custom feed new option

546a4fb

narefyev91 requested a review from a team as a code owner November 21, 2024 11:53

melvin-bot bot requested review from allgandalf and removed request for a team November 21, 2024 11:53

allgandalf reviewed Nov 21, 2024

View reviewed changes

src/languages/en.ts Show resolved Hide resolved

allgandalf reviewed Nov 21, 2024

View reviewed changes

src/languages/es.ts Outdated Show resolved Hide resolved

Update src/languages/es.ts

a5f1064

Co-authored-by: Gandalf <[email protected]>

narefyev91 requested a review from allgandalf November 21, 2024 13:07

allgandalf approved these changes Nov 21, 2024

View reviewed changes

melvin-bot bot requested a review from mountiny November 21, 2024 13:41

mountiny assigned narefyev91 Nov 21, 2024

mountiny added the InternalQA This pull request required internal QA label Nov 21, 2024

mountiny approved these changes Nov 21, 2024

View reviewed changes

mountiny merged commit 76e0d13 into Expensify:main Nov 21, 2024
18 checks passed

github-actions bot mentioned this pull request Nov 22, 2024

Deploy Checklist: New Expensify 2024-11-22 #52978

Closed

75 tasks

melvin-bot bot mentioned this pull request Nov 26, 2024

[HOLD for payment 2024-12-03] [$125] Polish updates to Amex card flow #52798

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Internal QA]: Add amex custom feed new option #52890

[Internal QA]: Add amex custom feed new option #52890

narefyev91 commented Nov 21, 2024

melvin-bot bot commented Nov 21, 2024

allgandalf Nov 21, 2024

narefyev91 Nov 21, 2024

allgandalf Nov 21, 2024

allgandalf Nov 21, 2024

allgandalf Nov 21, 2024

allgandalf commented Nov 21, 2024 •

edited

Loading

allgandalf left a comment •

edited

Loading

OSBotify commented Nov 21, 2024

github-actions bot commented Nov 22, 2024

joekaufmanexpensify commented Nov 25, 2024

github-actions bot commented Nov 26, 2024

[Internal QA]: Add amex custom feed new option #52890

[Internal QA]: Add amex custom feed new option #52890

Conversation

narefyev91 commented Nov 21, 2024

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Nov 21, 2024

allgandalf Nov 21, 2024

Choose a reason for hiding this comment

narefyev91 Nov 21, 2024

Choose a reason for hiding this comment

allgandalf Nov 21, 2024

Choose a reason for hiding this comment

allgandalf Nov 21, 2024

Choose a reason for hiding this comment

allgandalf Nov 21, 2024

Choose a reason for hiding this comment

allgandalf commented Nov 21, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

allgandalf left a comment • edited Loading

Choose a reason for hiding this comment

OSBotify commented Nov 21, 2024

github-actions bot commented Nov 22, 2024

joekaufmanexpensify commented Nov 25, 2024

github-actions bot commented Nov 26, 2024

allgandalf commented Nov 21, 2024 •

edited

Loading

allgandalf left a comment •

edited

Loading