[TS migration] Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript #32655

pasyukevich · 2023-12-07T12:41:10Z

Details

Fixed Issues

$ #31943
PROPOSAL:

Tests

User should be an employee of a Collect workspace
Log in to ND as the employee
Go to the workspace chat > "+" > Request money.
Create a manual request.
Click on the expense preview.
Verify that the header showed as expected for the money request

Verify that no errors appear in the JS console

Offline tests

QA Steps

User should be an employee of a Collect workspace
Log in to ND as the employee
Go to the workspace chat > "+" > Request money.
Create a manual request.
Click on the expense preview.
Verify that the header showed as expected for the money request

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

fabioh8010 · 2023-12-07T16:43:47Z

src/CONST.ts

+    NEXT_STEP: {
+        type: {
+            NEUTRAL: 'neutral',
+            ALERT: 'alert',
+            NULL: null,
+        },
+    },


I'm curious where do these values comes from?

We getting them from the Onyx

Please see my comment here.

src/types/onyx/ReportNextStep.ts

blazejkustra · 2023-12-14T14:33:52Z

Resolve conflicts, add screenshots, LGTM!

melvin-bot · 2023-12-15T16:27:59Z

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

hoangzinh · 2023-12-17T17:26: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 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(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 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

hoangzinh

LGTM

melvin-bot · 2023-12-17T17:57:49Z

We did not find an internal engineer to review this PR, trying to assign a random engineer to #31943 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

srikarparsi · 2023-12-18T18:10:57Z

Looks like there's a merge conflict @pasyukevich

pasyukevich · 2023-12-19T12:29:33Z

@srikarparsi conflict solved

srikarparsi

lgtm

OSBotify · 2023-12-20T08:10:30Z

✋ 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 · 2023-12-21T05:30:50Z

🚀 Deployed to staging by https://github.com/srikarparsi in version: 1.4.15-0 🚀

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

OSBotify · 2023-12-22T05:19:33Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.4.15-5 🚀

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

fabioh8010 reviewed Dec 7, 2023

View reviewed changes

fabioh8010 reviewed Dec 11, 2023

View reviewed changes

pasyukevich force-pushed the feature/migrate-MoneyReportHeaderStatusBar branch 2 times, most recently from 1a53df3 to 6bbea27 Compare December 11, 2023 16:00

fabioh8010 reviewed Dec 12, 2023

View reviewed changes

src/types/onyx/ReportNextStep.ts Outdated Show resolved Hide resolved

src/types/onyx/ReportNextStep.ts Outdated Show resolved Hide resolved

src/types/onyx/ReportNextStep.ts Outdated Show resolved Hide resolved

pasyukevich force-pushed the feature/migrate-MoneyReportHeaderStatusBar branch 3 times, most recently from 3405800 to 90200f1 Compare December 12, 2023 10:13

fabioh8010 approved these changes Dec 12, 2023

View reviewed changes

blazejkustra approved these changes Dec 14, 2023

View reviewed changes

Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript

480bdfa

pasyukevich force-pushed the feature/migrate-MoneyReportHeaderStatusBar branch from 90200f1 to 480bdfa Compare December 15, 2023 09:41

pasyukevich marked this pull request as ready for review December 15, 2023 16:27

pasyukevich requested a review from a team as a code owner December 15, 2023 16:27

melvin-bot bot requested review from hoangzinh and removed request for a team December 15, 2023 16:27

hoangzinh approved these changes Dec 17, 2023

View reviewed changes

melvin-bot bot requested a review from srikarparsi December 17, 2023 17:57

Merge branch 'main' into feature/migrate-MoneyReportHeaderStatusBar

db468c8

srikarparsi approved these changes Dec 20, 2023

View reviewed changes

srikarparsi merged commit c09a3fe into Expensify:main Dec 20, 2023

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

Deploy Checklist: New Expensify 2023-12-21 #33391

Closed

51 tasks

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

[HOLD for payment 2023-12-29] [TS migration] Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript #31943

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[TS migration] Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript #32655

[TS migration] Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript #32655

pasyukevich commented Dec 7, 2023 •

edited

Loading

fabioh8010 Dec 7, 2023

pasyukevich Dec 8, 2023

fabioh8010 Dec 11, 2023

blazejkustra commented Dec 14, 2023

melvin-bot bot commented Dec 15, 2023

hoangzinh commented Dec 17, 2023 •

edited

Loading

hoangzinh left a comment

melvin-bot bot commented Dec 17, 2023

srikarparsi commented Dec 18, 2023

pasyukevich commented Dec 19, 2023

srikarparsi left a comment

OSBotify commented Dec 20, 2023

OSBotify commented Dec 21, 2023

OSBotify commented Dec 22, 2023

[TS migration] Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript #32655

[TS migration] Migrate 'MoneyReportHeaderStatusBar.js' component to TypeScript #32655

Conversation

pasyukevich commented Dec 7, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

fabioh8010 Dec 7, 2023

Choose a reason for hiding this comment

pasyukevich Dec 8, 2023

Choose a reason for hiding this comment

fabioh8010 Dec 11, 2023

Choose a reason for hiding this comment

blazejkustra commented Dec 14, 2023

melvin-bot bot commented Dec 15, 2023

hoangzinh commented Dec 17, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

hoangzinh left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Dec 17, 2023

srikarparsi commented Dec 18, 2023

pasyukevich commented Dec 19, 2023

srikarparsi left a comment

Choose a reason for hiding this comment

OSBotify commented Dec 20, 2023

OSBotify commented Dec 21, 2023

OSBotify commented Dec 22, 2023

pasyukevich commented Dec 7, 2023 •

edited

Loading

hoangzinh commented Dec 17, 2023 •

edited

Loading