[TS migration] Migrate 'ArchivedReportFooter.js' component to TypeScript by VickyStash · Pull Request #31643 · Expensify/App

VickyStash · 2023-11-21T16:29:44Z

Details

[TS migration] Migrate 'ArchivedReportFooter.js' component to TypeScript

Fixed Issues

$ #25085
PROPOSAL: N/A

Tests

Verify that no errors appear in the JS console

Create a new workspace -> new admins chat will be created
Delete created workspace
Open the admin's chat of the deleted workspace. Make sure the footer with a banner looks ok and has a correct message about the inactive workspace.

Offline tests

N/A

QA Steps

Verify that no errors appear in the JS console

Create a new workspace -> new admins chat will be created
Delete created workspace
Open the admin's chat of the deleted workspace. Make sure the footer with a banner looks ok and has a correct message about the inactive workspace.

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

kubabutkiewicz

lgtm 😄

src/components/ArchivedReportFooter.tsx

blazejkustra · 2023-11-24T15:46:21Z

src/components/ArchivedReportFooter.tsx

+    const archiveReason = originalMessage?.reason ?? CONST.REPORT.ARCHIVE_REASON.DEFAULT;
+    let displayName = PersonalDetailsUtils.getDisplayNameOrDefault(personalDetails, [report.ownerAccountID, 'displayName']);
+
+    let oldDisplayName;


oldDisplayName is of type any, please define type in this line

blazejkustra · 2023-11-24T15:47:30Z

src/components/ArchivedReportFooter.tsx

+    report: Report;
+};
+
+function ArchivedReportFooter({report, reportClosedAction = null, personalDetails = {}}: ArchivedReportFooterProps) {


Does this work?

Suggested change

function ArchivedReportFooter({report, reportClosedAction = null, personalDetails = {}}: ArchivedReportFooterProps) {

function ArchivedReportFooter({report, reportClosedAction, personalDetails = {}}: ArchivedReportFooterProps) {

VickyStash · 2023-11-24T16:17:31Z

@blazejkustra Good point! Updated 🙂

melvin-bot · 2023-11-24T16:51:21Z

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

# Conflicts: # src/types/onyx/OriginalMessage.ts

Ollyws · 2023-11-28T12:30:08Z

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

Ollyws

LGTM.

melvin-bot · 2023-11-28T12:33:16Z

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

OSBotify · 2023-11-28T16:26:08Z

✋ 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-11-30T12:15:27Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.5-7 🚀

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

[TS migration] Migrate 'ArchivedReportFooter.js' component

8728cf3

kubabutkiewicz approved these changes Nov 22, 2023

View reviewed changes

fabioh8010 reviewed Nov 22, 2023

View reviewed changes

src/components/ArchivedReportFooter.tsx Show resolved Hide resolved

Minor code improvement

92e457a

fabioh8010 approved these changes Nov 22, 2023

View reviewed changes

blazejkustra suggested changes Nov 24, 2023

View reviewed changes

Add missed type

eb19a2f

blazejkustra approved these changes Nov 24, 2023

View reviewed changes

VickyStash marked this pull request as ready for review November 24, 2023 16:51

VickyStash requested a review from a team as a code owner November 24, 2023 16:51

melvin-bot bot requested review from Ollyws and removed request for a team November 24, 2023 16:51

Merge branch 'main' into ts-migration/archivedReportFooter-component

5be5158

# Conflicts: # src/types/onyx/OriginalMessage.ts

Ollyws approved these changes Nov 28, 2023

View reviewed changes

melvin-bot bot requested a review from pecanoro November 28, 2023 12:33

pecanoro approved these changes Nov 28, 2023

View reviewed changes

pecanoro merged commit 9b1f465 into Expensify:main Nov 28, 2023

github-actions bot mentioned this pull request Nov 29, 2023

Deploy Checklist: New Expensify 2023-11-29 #32175

Closed

55 tasks

melvin-bot bot mentioned this pull request Nov 30, 2023

[HOLD for payment 2023-12-07][$250][TS migration] Migrate 'ArchivedReportFooter.js' component to TypeScript #25085

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[TS migration] Migrate 'ArchivedReportFooter.js' component to TypeScript#31643

[TS migration] Migrate 'ArchivedReportFooter.js' component to TypeScript#31643
pecanoro merged 4 commits intoExpensify:mainfrom
VickyStash:ts-migration/archivedReportFooter-component

VickyStash commented Nov 21, 2023 •

edited

Loading

Uh oh!

kubabutkiewicz left a comment

Uh oh!

Uh oh!

blazejkustra Nov 24, 2023

Uh oh!

blazejkustra Nov 24, 2023

Uh oh!

VickyStash commented Nov 24, 2023

Uh oh!

melvin-bot bot commented Nov 24, 2023

Uh oh!

Ollyws commented Nov 28, 2023

Uh oh!

Ollyws left a comment

Uh oh!

melvin-bot bot commented Nov 28, 2023

Uh oh!

OSBotify commented Nov 28, 2023

Uh oh!

OSBotify commented Nov 30, 2023

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

	function ArchivedReportFooter({report, reportClosedAction = null, personalDetails = {}}: ArchivedReportFooterProps) {
	function ArchivedReportFooter({report, reportClosedAction, personalDetails = {}}: ArchivedReportFooterProps) {

Conversation

VickyStash commented Nov 21, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

kubabutkiewicz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

blazejkustra Nov 24, 2023

Choose a reason for hiding this comment

Uh oh!

blazejkustra Nov 24, 2023

Choose a reason for hiding this comment

Uh oh!

VickyStash commented Nov 24, 2023

Uh oh!

melvin-bot bot commented Nov 24, 2023

Uh oh!

Ollyws commented Nov 28, 2023

Reviewer Checklist

Screenshots/Videos

Uh oh!

Ollyws left a comment

Choose a reason for hiding this comment

Uh oh!

melvin-bot bot commented Nov 28, 2023

Uh oh!

OSBotify commented Nov 28, 2023

Uh oh!

OSBotify commented Nov 30, 2023

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

VickyStash commented Nov 21, 2023 •

edited

Loading