[CP Staging] fix: bank account flow - inscription text style #33141

neonbhai · 2023-12-15T04:02:45Z

Details

Fixed Issues

$ #33135
PROPOSAL: #33135 (comment)

Tests

Go to Settings -> Workspaces -> Open any WS -> Connect BA -> Connect via Plaid -> Chace
Go through the process until the Additional Information page
Open the form for an additional beneficial owner
Fill Checkbox for on Somebody else owns more than 25%
Verify Additional beneficial owner is visible

Verify that no errors appear in the JS console

To directly reach ACH Step on Dev

Step 1: Comment this block

Step 2:
Paste this above the commented block:

if (currentStep === CONST.BANK_ACCOUNT.STEP.BANK_ACCOUNT) {
    return (
        <ACHContractStep
            reimbursementAccount={reimbursementAccount}
            reimbursementAccountDraft={reimbursementAccountDraft}
            onBackButtonPress={goBack}
            companyName={achData.companyName}
            getDefaultStateForField={getDefaultStateForField}
        />
    );
}

Offline tests

Same as Tests Step

QA Steps

Same as Tests Step

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2023-12-15.at.9.15.00.AM.mov

Screen.Recording.2023-12-15.at.9.15.59.AM.mov

MacOS: Desktop

melvin-bot · 2023-12-15T04:02:50Z

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

jasperhuangg · 2023-12-15T06:12:18Z

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

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

OSBotify · 2023-12-15T06:21:56Z

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

fix: bank account flow - inscription text style (cherry picked from commit 3a44f77)

OSBotify · 2023-12-19T02:02:43Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.4.13-8 🚀

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

Fix header text style

1234afe

neonbhai requested a review from a team as a code owner December 15, 2023 04:02

melvin-bot bot requested review from thesahindia and removed request for a team December 15, 2023 04:02

jasperhuangg approved these changes Dec 15, 2023

View reviewed changes

jasperhuangg removed the request for review from thesahindia December 15, 2023 06:16

jasperhuangg merged commit 3a44f77 into Expensify:main Dec 15, 2023
16 of 18 checks passed

OSBotify pushed a commit that referenced this pull request Dec 15, 2023

Merge pull request #33141 from neonbhai/achcontractstep-style-fix

3f50a0a

fix: bank account flow - inscription text style (cherry picked from commit 3a44f77)

github-actions bot mentioned this pull request Dec 15, 2023

Deploy Checklist: New Expensify 2023-12-14 #33072

Closed

77 tasks

Julesssss assigned neonbhai Dec 15, 2023

mountiny changed the title ~~fix: bank account flow - inscription text style~~ [CP Staging] fix: bank account flow - inscription text style Dec 15, 2023

melvin-bot bot mentioned this pull request Dec 19, 2023

[HOLD for payment 2023-12-28] [HOLD for payment 2023-12-26] Connect Bank account - Inscription Additional beneficial owner is invisible on the page of beneficial owners #33135

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] fix: bank account flow - inscription text style #33141

[CP Staging] fix: bank account flow - inscription text style #33141

neonbhai commented Dec 15, 2023 •

edited

Loading

melvin-bot bot commented Dec 15, 2023

jasperhuangg commented Dec 15, 2023 •

edited

Loading

OSBotify commented Dec 15, 2023

OSBotify commented Dec 19, 2023

[CP Staging] fix: bank account flow - inscription text style #33141

[CP Staging] fix: bank account flow - inscription text style #33141

Conversation

neonbhai commented Dec 15, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Dec 15, 2023

jasperhuangg commented Dec 15, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

OSBotify commented Dec 15, 2023

OSBotify commented Dec 19, 2023

neonbhai commented Dec 15, 2023 •

edited

Loading

jasperhuangg commented Dec 15, 2023 •

edited

Loading