Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TS migration] Migrate 'Tooltip' component to TypeScript #31544

Merged
merged 31 commits into from
Dec 8, 2023

Conversation

kosmydel
Copy link
Contributor

@kosmydel kosmydel commented Nov 20, 2023

Details

Fixed Issues

$ #25123
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console
  • On web and desktop:
    • Hover the buttons with tooltips (Search button, account settings button, FAB). Verify tooltips are correctly displayed.
  • Verify that the app works.

Offline tests

N/A

QA Steps

  • Verify that no errors appear in the JS console
  • Tests from above.

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

Screenshots/Videos

Android: Native Screenshot 2023-11-28 at 15 23 45
Android: mWeb Chrome Screenshot 2023-11-28 at 15 23 45
iOS: Native

Simulator Screenshot - iPhone 15 Pro - 2023-11-28 at 15 24 25

iOS: mWeb Safari

Simulator Screenshot - iPhone 15 Pro - 2023-11-28 at 15 25 28

MacOS: Chrome / Safari
Screen.Recording.2023-11-28.at.15.16.53.mov
MacOS: Desktop
Screen.Recording.2023-11-28.at.15.19.32.mov

src/components/DisplayNames/DisplayNamesTooltipItem.tsx Outdated Show resolved Hide resolved
src/components/Pressable/PressableWithDelayToggle.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/BaseTooltip.native.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/BaseTooltip.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/BaseTooltip.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/types.ts Show resolved Hide resolved
src/types/utils/callOrReturn.ts Outdated Show resolved Hide resolved
src/styles/getTooltipStyles.ts Outdated Show resolved Hide resolved
src/components/Tooltip/BaseTooltip.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/TooltipRenderedOnPageBody.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/PopoverAnchorTooltip.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/BaseTooltip.tsx Outdated Show resolved Hide resolved
src/components/Tooltip/BaseTooltip.tsx Outdated Show resolved Hide resolved
Copy link
Contributor

@BartoszGrajdek BartoszGrajdek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's also move BaseTooltip files into a separate folder src/components/Tooltip/BaseTooltip/....

src/components/Tooltip/BaseTooltip.native.tsx Outdated Show resolved Hide resolved
Copy link
Contributor

@BartoszGrajdek BartoszGrajdek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@kosmydel
Copy link
Contributor Author

kosmydel commented Dec 6, 2023

Hey, I pulled the main, resolved conflicts, and had to make fix warning on native on native, as there was a warning during runtime (related to forwardRef, web version used is while native didn't).

cc @blazejkustra, @allroundexperts

Copy link
Contributor

@allroundexperts allroundexperts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving since this is catching conflicts so fast. This is testing well and should be good to merge!

@kosmydel
Copy link
Contributor Author

kosmydel commented Dec 7, 2023

I've resolved conflicts, so it is ready to proceed.

Copy link
Contributor

@allroundexperts allroundexperts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got an internal engineer!

@melvin-bot melvin-bot bot requested a review from joelbettner December 7, 2023 08:53
@kosmydel
Copy link
Contributor Author

kosmydel commented Dec 8, 2023

I've resolved conflicts once again. cc @blazejkustra @allroundexperts

@mountiny mountiny requested review from mountiny and removed request for joelbettner December 8, 2023 11:40
@mountiny
Copy link
Contributor

mountiny commented Dec 8, 2023

Gonna take it over here as its component with lots of conflicts to get it over the finish line

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok lets go, thank you for patience @kosmydel and testing thoroughly @allroundexperts

/** Unique key of renderTooltipContent to rerender the tooltip when one of the key changes */
renderTooltipContentKey?: string[];

/** passes this down to Hoverable component to decide whether to handle the scroll behaviour to show hover once the scroll ends */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB

Suggested change
/** passes this down to Hoverable component to decide whether to handle the scroll behaviour to show hover once the scroll ends */
/** Passes this down to Hoverable component to decide whether to handle the scroll behaviour to show hover once the scroll ends */

@mountiny mountiny merged commit 18d4b9b into Expensify:main Dec 8, 2023
18 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Dec 8, 2023

✋ 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
Copy link
Contributor

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

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.11-25 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants