[TS Migration] Migrate CopyTextToClipboard.js to TypeScript #31486

JKobrynski · 2023-11-17T12:35:06Z

Details

Fixed Issues

$ #25011
PROPOSAL: N/A

Tests

Log into the app
Navigate to the Settings page
Navigate to the Profile page
Navigate to the Contact Method page
Use the icon next to highlighted email address to copy it to your clipboard, make sure it works

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as Tests section above

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

android-compressed.webm

Android: Web

chrome-compressed.webm

iOS: Native

ios-compressed.mp4

iOS: mWeb Safari

safari-compressed.mp4

MacOS: Chrome / Safari

web-compressed.mov

MacOS: Desktop

desktop-compressed.mov

src/components/CopyTextToClipboard.tsx

BartoszGrajdek

LGTM!

melvin-bot · 2023-11-20T14:44:20Z

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

mountiny · 2023-11-22T11:32:41Z

@burczu Can you please do checklist on this PR?

burczu · 2023-11-22T11:56:36Z

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

Screen.Recording.2023-11-22.at.13.20.41.mov

Android: mWeb Chrome

Screen.Recording.2023-11-22.at.13.25.03.mov

iOS: Native

Screen.Recording.2023-11-22.at.13.18.58.mov

iOS: mWeb Safari

Screen.Recording.2023-11-22.at.13.22.28.mov

MacOS: Chrome / Safari

Screen.Recording.2023-11-22.at.13.25.50.mov

MacOS: Desktop

Screen.Recording.2023-11-22.at.13.27.24.mov

burczu · 2023-11-22T11:57:58Z

@JKobrynski Is screenshot for Android: mWeb missing for a reason? :)

JKobrynski · 2023-11-22T12:26:04Z

@burczu no reason 😄

burczu · 2023-11-22T12:29:00Z

@JKobrynski Please update it because I can't check this checkbox without it 🤷‍♂️

[ ] I checked that screenshots or videos are included for tests on [all platforms]

JKobrynski · 2023-11-27T10:32:33Z

@burczu video uploaded 😄

burczu

LGTM

melvin-bot · 2023-11-27T10:33:49Z

🎯 @burczu, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #31901.

JKobrynski · 2023-12-12T09:35:36Z

@mountiny could you help with getting this assigned to some reviewer? 🙏

mountiny · 2023-12-12T12:24:57Z

src/components/CopyTextToClipboard.tsx

+            textStyles={textStyles}
+            onPress={copyToClipboard}
+            accessible
+            accessibilityLabel={translate('reportActionContextMenu.copyEmailToClipboard')}


Is this the correct label in this case? copyEmailToClipboard? It can be other things than email right?

right, my bad

mountiny · 2023-12-12T12:38:01Z

src/components/CopyTextToClipboard.tsx

+            textStyles={textStyles}
+            onPress={copyToClipboard}
+            accessible
+            accessibilityLabel={translate('reportActionContextMenu.copyEmailToClipboard')}


Suggested change

accessibilityLabel={translate('reportActionContextMenu.copyEmailToClipboard')}

accessibilityLabel={translate('reportActionContextMenu.copyToClipboard')}

mountiny

Thank you @JKobrynski

OSBotify · 2023-12-13T13:25:00Z

✋ 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-14T16:05:31Z

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

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

OSBotify · 2023-12-14T16:45:19Z

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

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

OSBotify · 2023-12-19T02:01:37Z

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

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

migrate CopyTextToClipboard.js to TypeScript

a7f5672

kubabutkiewicz reviewed Nov 17, 2023

View reviewed changes

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

JKobrynski added 2 commits November 20, 2023 08:39

remove WithLocalizeProps from CopyTextTOClipboardProps

7fd35bc

Merge branch 'main' into migrateCopyTextToClipboardToTypeScript

9fa22aa

JKobrynski requested a review from kubabutkiewicz November 20, 2023 07:42

fabioh8010 reviewed Nov 20, 2023

View reviewed changes

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

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

destructure props, add coment to eslint disable

abf847e

JKobrynski requested a review from fabioh8010 November 20, 2023 09:14

fabioh8010 approved these changes Nov 20, 2023

View reviewed changes

BartoszGrajdek approved these changes Nov 20, 2023

View reviewed changes

JKobrynski marked this pull request as ready for review November 20, 2023 14:44

JKobrynski requested a review from a team as a code owner November 20, 2023 14:44

melvin-bot bot removed request for a team and kubabutkiewicz November 20, 2023 14:44

JKobrynski mentioned this pull request Nov 20, 2023

[HOLD for payment 2023-12-26] [TS migration] Migrate 'CopyTextToClipboard.js' component to TypeScript #25011

Closed

mountiny requested a review from burczu November 22, 2023 11:32

Merge branch 'main' into migrateCopyTextToClipboardToTypeScript

194398a

burczu approved these changes Nov 27, 2023

View reviewed changes

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

Payment issue for E/App PR#31486 #31901

Closed

mountiny assigned JKobrynski Dec 12, 2023

mountiny self-requested a review December 12, 2023 11:03

Merge branch 'main' into migrateCopyTextToClipboardToTypeScript

6d2c64f

mountiny requested changes Dec 12, 2023

View reviewed changes

change accessibility label

42e7f61

JKobrynski requested a review from mountiny December 12, 2023 13:41

mountiny approved these changes Dec 13, 2023

View reviewed changes

mountiny merged commit 2782381 into Expensify:main Dec 13, 2023
17 checks passed

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

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

Closed

77 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[TS Migration] Migrate CopyTextToClipboard.js to TypeScript #31486

[TS Migration] Migrate CopyTextToClipboard.js to TypeScript #31486

JKobrynski commented Nov 17, 2023 •

edited by mountiny

Loading

BartoszGrajdek left a comment

melvin-bot bot commented Nov 20, 2023

mountiny commented Nov 22, 2023

burczu commented Nov 22, 2023 •

edited

Loading

burczu commented Nov 22, 2023

JKobrynski commented Nov 22, 2023

burczu commented Nov 22, 2023

JKobrynski commented Nov 27, 2023

burczu left a comment

melvin-bot bot commented Nov 27, 2023

JKobrynski commented Dec 12, 2023

mountiny Dec 12, 2023

JKobrynski Dec 12, 2023

mountiny Dec 12, 2023

JKobrynski Dec 12, 2023

mountiny left a comment

OSBotify commented Dec 13, 2023

OSBotify commented Dec 14, 2023

OSBotify commented Dec 14, 2023

OSBotify commented Dec 19, 2023

	accessibilityLabel={translate('reportActionContextMenu.copyEmailToClipboard')}
	accessibilityLabel={translate('reportActionContextMenu.copyToClipboard')}

[TS Migration] Migrate CopyTextToClipboard.js to TypeScript #31486

[TS Migration] Migrate CopyTextToClipboard.js to TypeScript #31486

Conversation

JKobrynski commented Nov 17, 2023 • edited by mountiny Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

BartoszGrajdek left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Nov 20, 2023

mountiny commented Nov 22, 2023

burczu commented Nov 22, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

burczu commented Nov 22, 2023

JKobrynski commented Nov 22, 2023

burczu commented Nov 22, 2023

JKobrynski commented Nov 27, 2023

burczu left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Nov 27, 2023

JKobrynski commented Dec 12, 2023

mountiny Dec 12, 2023

Choose a reason for hiding this comment

JKobrynski Dec 12, 2023

Choose a reason for hiding this comment

mountiny Dec 12, 2023

Choose a reason for hiding this comment

JKobrynski Dec 12, 2023

Choose a reason for hiding this comment

mountiny left a comment

Choose a reason for hiding this comment

OSBotify commented Dec 13, 2023

OSBotify commented Dec 14, 2023

OSBotify commented Dec 14, 2023

OSBotify commented Dec 19, 2023

JKobrynski commented Nov 17, 2023 •

edited by mountiny

Loading

burczu commented Nov 22, 2023 •

edited

Loading