[No QA] [TS migration] Migrate 'cardStyles' style to TypeScript #25886

pasyukevich · 2023-08-24T19:53:49Z

Details

Fixed Issues

$ #24714

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

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 / Chrome
- iOS / native
- iOS / 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

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

fabioh8010 · 2023-08-25T09:53:06Z

src/styles/cardStyles/types.ts

@@ -0,0 +1,5 @@
+import {CSSProperties} from 'react';
+
+type GetCardStyles = (isSmallScreenWidth: boolean, screenWidth: number) => Partial<Pick<CSSProperties, 'position' | 'width' | 'right' | 'height'>>;


melvin-bot · 2023-08-25T15:12:55Z

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

pasyukevich · 2023-08-25T15:13:09Z

@blazejkustra PR is ready for review!

melvin-bot · 2023-08-25T15:20:38Z

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

blazejkustra

Only one comment, also agree with Fabio's comment. Other than that LGTM!

blazejkustra · 2023-08-27T14:31:20Z

src/styles/cardStyles/index.ts

+import variables from '../variables';
+import GetCardStyles from './types';
+
+// Get card style for cardStyleInterpolator


For better intellisense:

Suggested change

// Get card style for cardStyleInterpolator

/** Get card style for cardStyleInterpolator */

srikarparsi · 2023-08-28T20:38: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 / Chrome
- iOS / native
- iOS / 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

srikarparsi · 2023-08-28T23:33:30Z

Hi @pasyukevich, can you add the other screenshots whenever you get a chance?

pasyukevich · 2023-08-29T12:19:15Z

Hi @srikarparsi,

I was instructed to have at least web screenshots for such updates
I also added ios and desktop

srikarparsi · 2023-08-31T01:36:40Z

Ah got it thanks! It looks like there's a conflict now but once that's fixed, this seems good to merge

roryabraham · 2023-09-12T10:27:40Z

Bump to resolve conflicts

pasyukevich · 2023-09-12T16:39:27Z

rebased with solved conflicts

srikarparsi

lgtm

OSBotify · 2023-09-13T08:11:11Z

✋ 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-09-13T09:12:35Z

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

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

OSBotify · 2023-09-14T10:26:49Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.69-2 🚀

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

OSBotify · 2023-09-14T10:53:37Z

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

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

OSBotify · 2023-09-18T10:11:36Z

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.70-8 🚀

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

fabioh8010 reviewed Aug 25, 2023

View reviewed changes

pasyukevich force-pushed the migration-ts/card-styles branch from e9304bd to 42c02fb Compare August 25, 2023 13:32

pasyukevich marked this pull request as ready for review August 25, 2023 15:12

pasyukevich requested a review from a team as a code owner August 25, 2023 15:12

melvin-bot bot requested review from ntdiary and removed request for a team August 25, 2023 15:12

ntdiary approved these changes Aug 25, 2023

View reviewed changes

melvin-bot bot requested a review from srikarparsi August 25, 2023 15:20

blazejkustra approved these changes Aug 27, 2023

View reviewed changes

migrate 'cardStyles' to ts

76ffe96

pasyukevich force-pushed the migration-ts/card-styles branch from 42c02fb to 76ffe96 Compare September 12, 2023 16:38

srikarparsi approved these changes Sep 13, 2023

View reviewed changes

srikarparsi merged commit 0df67e1 into Expensify:main Sep 13, 2023
11 checks passed

OSBotify mentioned this pull request Sep 13, 2023

Deploy Checklist: New Expensify 2023-09-13 #27313

Closed

72 tasks

OSBotify mentioned this pull request Sep 14, 2023

Deploy Checklist: New Expensify 2023-09-14 #27425

Closed

melvin-bot bot mentioned this pull request Sep 14, 2023

[HOLD for payment 2023-09-21] [TS migration] Migrate 'cardStyles' style to TypeScript #24714

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA] [TS migration] Migrate 'cardStyles' style to TypeScript #25886

[No QA] [TS migration] Migrate 'cardStyles' style to TypeScript #25886

pasyukevich commented Aug 24, 2023 •

edited

Loading

fabioh8010 Aug 25, 2023

melvin-bot bot commented Aug 25, 2023

pasyukevich commented Aug 25, 2023

melvin-bot bot commented Aug 25, 2023

blazejkustra left a comment

blazejkustra Aug 27, 2023

srikarparsi commented Aug 28, 2023 •

edited

Loading

srikarparsi commented Aug 28, 2023

pasyukevich commented Aug 29, 2023

srikarparsi commented Aug 31, 2023

roryabraham commented Sep 12, 2023

pasyukevich commented Sep 12, 2023

srikarparsi left a comment

OSBotify commented Sep 13, 2023

OSBotify commented Sep 13, 2023

OSBotify commented Sep 14, 2023

OSBotify commented Sep 14, 2023

OSBotify commented Sep 18, 2023

		@@ -0,0 +1,5 @@
		import {CSSProperties} from 'react';

		type GetCardStyles = (isSmallScreenWidth: boolean, screenWidth: number) => Partial<Pick<CSSProperties, 'position' \| 'width' \| 'right' \| 'height'>>;

	// Get card style for cardStyleInterpolator
	/** Get card style for cardStyleInterpolator */

[No QA] [TS migration] Migrate 'cardStyles' style to TypeScript #25886

[No QA] [TS migration] Migrate 'cardStyles' style to TypeScript #25886

Conversation

pasyukevich commented Aug 24, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

fabioh8010 Aug 25, 2023

Choose a reason for hiding this comment

melvin-bot bot commented Aug 25, 2023

pasyukevich commented Aug 25, 2023

melvin-bot bot commented Aug 25, 2023

blazejkustra left a comment

Choose a reason for hiding this comment

blazejkustra Aug 27, 2023

Choose a reason for hiding this comment

srikarparsi commented Aug 28, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

srikarparsi commented Aug 28, 2023

pasyukevich commented Aug 29, 2023

srikarparsi commented Aug 31, 2023

roryabraham commented Sep 12, 2023

pasyukevich commented Sep 12, 2023

srikarparsi left a comment

Choose a reason for hiding this comment

OSBotify commented Sep 13, 2023

OSBotify commented Sep 13, 2023

OSBotify commented Sep 14, 2023

OSBotify commented Sep 14, 2023

OSBotify commented Sep 18, 2023

pasyukevich commented Aug 24, 2023 •

edited

Loading

srikarparsi commented Aug 28, 2023 •

edited

Loading