[No QA] [TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript #29547

VickyStash · 2023-10-13T11:24:47Z

Details

[TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript

Fixed Issues

$ #24961
PROPOSAL: N/A

Tests

Verify that no errors appear in the JS console

This HOC is used throughout the whole app. Make sure current user details are displayed correctly.

Test case example:

Open the app
Tap on the avatar in the sidebar to open Settings -> verify the user data is displayed correctly.
Go to Profile -> verify the user data is displayed correctly there as well.

Offline tests

N/A

QA Steps

Verify that no errors appear in the JS console

This HOC is used throughout the whole app. Make sure current user details are displayed correctly.

Test case example:

Open the app
Tap on the avatar in the sidebar to open Settings -> verify the user data is displayed correctly.
Go to Profile -> verify the user data is displayed correctly there as well.

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 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
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- 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 author 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

kubabutkiewicz

LGTM 😄

src/components/withCurrentUserPersonalDetails.tsx

VickyStash · 2023-10-16T17:04:09Z

@blazejkustra I've updated the PR with some of your recommendations, but I still have some doubts about the return type, I'll return back to it tomorrow morning

blazejkustra

LGTM

src/components/withCurrentUserPersonalDetails.tsx

melvin-bot · 2023-10-17T10:51:11Z

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

Ollyws · 2023-10-19T12:05:22Z

I don't know if this one needs to be QA'd. In the case that it is could we update the testing steps to read:

Navigate to Settings > Profile
Verify the user data is displayed correctly

Ollyws · 2023-10-19T12:08:53Z

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

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Ollyws

LGTM.

melvin-bot · 2023-10-19T12:09:28Z

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

VickyStash · 2023-10-19T12:14:20Z

@Ollyws Sure, I've updated the testing steps

dangrous · 2023-10-19T14:59:44Z

I'm getting a crash on web when testing this; I'm pretty sure it's unrelated but do you mind merging main into this PR to see if that solves it?

Click on avatar to open settings
Click on Profile
Click on Pronouns
Update or click on any pronouns
Click the < to the left of Profile in the header

Console error below. It's not happening on main so I wanted to bring it up.

Uncaught TypeError: Cannot read properties of undefined (reading 'width')
    at Object.updateBounds [as onBoundsChange] (BaseTooltip.js:171:1)
    at exports.BoundsObserver.BoundsObserver._activate (index.js:123:1)
    at exports.BoundsObserver.BoundsObserver._observe (index.js:115:1)
    at handleCallbackUpdate (index.js:68:1)
    at exports.BoundsObserver.BoundsObserver.componentDidUpdate (index.js:80:1)
    at commitLayoutEffectOnFiber (react-dom.development.js:23232:1)
    at commitLayoutMountEffects_complete (react-dom.development.js:24578:1)
    at commitLayoutEffects_begin (react-dom.development.js:24564:1)
    at commitLayoutEffects (react-dom.development.js:24502:1)
    at commitRootImpl (react-dom.development.js:26779:1)

VickyStash · 2023-10-19T15:32:18Z

@dangrous You are right, it's resolved after merging the main

dangrous · 2023-10-19T20:56:05Z

src/components/withCurrentUserPersonalDetails.tsx

+        const accountID = props.session?.accountID ?? 0;
+        const accountPersonalDetails = props.personalDetails?.[accountID];


Just one question - can these be null (i.e. do they need the ?s? Seems like they'll always be there, right? Not marked as optional in OnyxProps...

@dangrous Since session and personalDetails are OnyxEntry, and OnyxEntry can be null, we need the ?s.

dangrous

Cool, makes sense to me!

OSBotify · 2023-10-20T15:26:14Z

✋ 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-10-20T21:37:21Z

🚀 Deployed to staging by https://github.com/dangrous in version: 1.3.88-0 🚀

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

OSBotify · 2023-10-23T04:49:33Z

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.88-11 🚀

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

[TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC

5d7ec0c

kubabutkiewicz approved these changes Oct 13, 2023

View reviewed changes

blazejkustra reviewed Oct 16, 2023

View reviewed changes

src/components/withCurrentUserPersonalDetails.tsx Outdated Show resolved Hide resolved

blazejkustra suggested changes Oct 16, 2023

View reviewed changes

Update withCurrentUserPersonalDetails HOC typing

5342f99

blazejkustra approved these changes Oct 17, 2023

View reviewed changes

src/components/withCurrentUserPersonalDetails.tsx Outdated Show resolved Hide resolved

src/components/withCurrentUserPersonalDetails.tsx Show resolved Hide resolved

Use OnyxEntry for the onyx type

5d016ef

VickyStash marked this pull request as ready for review October 17, 2023 10:51

VickyStash requested a review from a team as a code owner October 17, 2023 10:51

melvin-bot bot requested review from Ollyws and removed request for a team October 17, 2023 10:51

Ollyws approved these changes Oct 19, 2023

View reviewed changes

melvin-bot bot requested a review from dangrous October 19, 2023 12:09

Merge branch 'main' into ts-migration/withCurrentUserPersonalDetails-hoc

8ab35de

dangrous reviewed Oct 19, 2023

View reviewed changes

dangrous approved these changes Oct 20, 2023

View reviewed changes

dangrous merged commit 212e405 into Expensify:main Oct 20, 2023
15 checks passed

OSBotify mentioned this pull request Oct 20, 2023

Deploy Checklist: New Expensify 2023-10-20 #30108

Closed

melvin-bot bot mentioned this pull request Oct 23, 2023

[HOLD for payment 2023-10-30] [TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript #24961

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA] [TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript #29547

[No QA] [TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript #29547

VickyStash commented Oct 13, 2023 •

edited

Loading

kubabutkiewicz left a comment

VickyStash commented Oct 16, 2023

blazejkustra left a comment

melvin-bot bot commented Oct 17, 2023

Ollyws commented Oct 19, 2023

Ollyws commented Oct 19, 2023

Ollyws left a comment

melvin-bot bot commented Oct 19, 2023

VickyStash commented Oct 19, 2023

dangrous commented Oct 19, 2023

VickyStash commented Oct 19, 2023

dangrous Oct 19, 2023

VickyStash Oct 20, 2023

dangrous left a comment

OSBotify commented Oct 20, 2023

OSBotify commented Oct 20, 2023

OSBotify commented Oct 23, 2023

		const accountID = props.session?.accountID ?? 0;
		const accountPersonalDetails = props.personalDetails?.[accountID];

[No QA] [TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript #29547

[No QA] [TS migration] Migrate 'withCurrentUserPersonalDetails.js' HOC to TypeScript #29547

Conversation

VickyStash commented Oct 13, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

kubabutkiewicz left a comment

Choose a reason for hiding this comment

VickyStash commented Oct 16, 2023

blazejkustra left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Oct 17, 2023

Ollyws commented Oct 19, 2023

Ollyws commented Oct 19, 2023

Reviewer Checklist

Screenshots/Videos

Ollyws left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Oct 19, 2023

VickyStash commented Oct 19, 2023

dangrous commented Oct 19, 2023

VickyStash commented Oct 19, 2023

dangrous Oct 19, 2023

Choose a reason for hiding this comment

VickyStash Oct 20, 2023

Choose a reason for hiding this comment

dangrous left a comment

Choose a reason for hiding this comment

OSBotify commented Oct 20, 2023

OSBotify commented Oct 20, 2023

OSBotify commented Oct 23, 2023

VickyStash commented Oct 13, 2023 •

edited

Loading