[TS migration] Migrate 'SettingsInitial' page to TypeScript #36415

kubabutkiewicz · 2024-02-13T14:38:32Z

Details

Fixed Issues

$ #25202

Tests

Log into app
Go to Settings
Verify that Initial Settings Page looks and works as expected

Verify that no errors appear in the JS console

Offline tests

QA Steps

Log into app
Go to Settings
Verify that Initial Settings Page looks and works as expected

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(theme.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 the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

…s-migration/SettingInitial-page

src/pages/settings/InitialSettingsPage.tsx

…s-migration/SettingInitial-page

fabioh8010 · 2024-02-15T11:58:16Z

@kubabutkiewicz Please remove [No QA] prefix from PR title, this one isn't a leaf file like tests and should be tested by QA.

fabioh8010 · 2024-02-20T11:57:56Z

src/types/modules/react-native.d.ts

@@ -8,6 +8,10 @@ import type {CSSProperties, FocusEventHandler, KeyboardEventHandler, MouseEventH
 import 'react-native';
 import type {BootSplashModule} from '@libs/BootSplash/types';

+interface HybridAppModule {


Change interface to type

…s-migration/SettingInitial-page

melvin-bot · 2024-02-21T13:52:51Z

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

…s-migration/SettingInitial-page

allroundexperts · 2024-02-23T08:06:18Z

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(theme.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 the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
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

Screen.Recording.2024-02-26.at.12.39.52.PM.mov

MacOS: Chrome / Safari

MacOS: Desktop

allroundexperts · 2024-02-26T07:45:29Z

@kubabutkiewicz Looking good. Can you please resolve the conflicts?

kubabutkiewicz · 2024-02-26T08:41:59Z

sure , will do that today

kubabutkiewicz · 2024-02-26T09:35:26Z

src/pages/settings/InitialSettingsPage.tsx

-            );
+                },
+                ...defaultMenu.items,
+            ].filter((item) => item.translationKey !== 'initialSettingsPage.signOut' && item.translationKey !== 'exitSurvey.goToExpensifyClassic');


@allroundexperts Changing this key since this looked like a mistake because it was always false

allroundexperts

Looks good!

melvin-bot · 2024-02-26T10:23:04Z

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

bondydaa

just one minor question but i dont think it needs to block this PR.

bondydaa · 2024-02-26T16:56:56Z

src/styles/index.ts

@@ -2641,7 +2641,7 @@ const styles = (theme: ThemeColors) =>
            paddingLeft: 13,
            fontSize: 13,
            fontFamily: FontUtils.fontFamily.platform.EXP_NEUE,
-            fontWeight: 400,
+            fontWeight: '400',


should we use this constant instead?

App/src/styles/utils/FontUtils/index.ts

Line 14 in b4118ba

normal: '400',

OSBotify · 2024-02-26T17:03:49Z

✋ 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 · 2024-02-26T21:07:14Z

🚀 Deployed to staging by https://github.com/bondydaa in version: 1.4.44-0 🚀

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

OSBotify · 2024-02-28T23:55:50Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.44-13 🚀

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

kubabutkiewicz added 4 commits February 13, 2024 15:18

ref: move InitalSettingsPage to TS

a18dd9c

Merge branch 'main' of github.com:kubabutkiewicz/expensify-app into t…

daf8d8e

…s-migration/SettingInitial-page

fix: typecheck

c8dc983

Merge branch 'main' of github.com:kubabutkiewicz/expensify-app into t…

fb92f83

…s-migration/SettingInitial-page

fabioh8010 reviewed Feb 14, 2024

View reviewed changes

src/pages/settings/InitialSettingsPage.tsx Show resolved Hide resolved

src/pages/settings/InitialSettingsPage.tsx Show resolved Hide resolved

src/pages/settings/InitialSettingsPage.tsx Outdated Show resolved Hide resolved

kubabutkiewicz added 3 commits February 14, 2024 15:05

Merge branch 'main' of github.com:kubabutkiewicz/expensify-app into t…

a1c7b0f

…s-migration/SettingInitial-page

fix: resolve comments

90f9129

fix: prettier

0a94556

kubabutkiewicz changed the title ~~[No QA] [TS migration] Migrate 'SettingsInitial' page to TypeScript~~ [TS migration] Migrate 'SettingsInitial' page to TypeScript Feb 15, 2024

kubabutkiewicz added 4 commits February 15, 2024 16:58

Merge branch 'main' into ts-migration/SettingInitial-page

8ea4328

fix: address comments

c2d32ef

Merge branch 'main' into ts-migration/SettingInitial-page

33dd161

fix: typecheck

a85924b

fabioh8010 approved these changes Feb 20, 2024

View reviewed changes

fix: resolve comments

0c8e4c2

blazejkustra approved these changes Feb 20, 2024

View reviewed changes

Merge branch 'main' of github.com:kubabutkiewicz/expensify-app into t…

5f8ba92

…s-migration/SettingInitial-page

kubabutkiewicz marked this pull request as ready for review February 21, 2024 13:52

kubabutkiewicz requested a review from a team as a code owner February 21, 2024 13:52

melvin-bot bot removed the request for review from a team February 21, 2024 13:52

melvin-bot bot requested a review from allroundexperts February 21, 2024 13:52

Merge branch 'main' of github.com:kubabutkiewicz/expensify-app into t…

aca947b

…s-migration/SettingInitial-page

Merge branch 'main' into ts-migration/SettingInitial-page

b1b7880

kubabutkiewicz commented Feb 26, 2024

View reviewed changes

allroundexperts approved these changes Feb 26, 2024

View reviewed changes

melvin-bot bot requested a review from bondydaa February 26, 2024 10:23

bondydaa approved these changes Feb 26, 2024

View reviewed changes

bondydaa merged commit 5dc4c07 into Expensify:main Feb 26, 2024
19 checks passed

github-actions bot mentioned this pull request Feb 26, 2024

Deploy Checklist: New Expensify 2024-02-26 #37224

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[TS migration] Migrate 'SettingsInitial' page to TypeScript #36415

[TS migration] Migrate 'SettingsInitial' page to TypeScript #36415

kubabutkiewicz commented Feb 13, 2024 •

edited

Loading

fabioh8010 commented Feb 15, 2024

fabioh8010 Feb 20, 2024

melvin-bot bot commented Feb 21, 2024

allroundexperts commented Feb 23, 2024 •

edited

Loading

allroundexperts commented Feb 26, 2024

kubabutkiewicz commented Feb 26, 2024

kubabutkiewicz Feb 26, 2024

allroundexperts left a comment

melvin-bot bot commented Feb 26, 2024

bondydaa left a comment

bondydaa Feb 26, 2024

OSBotify commented Feb 26, 2024

OSBotify commented Feb 26, 2024

OSBotify commented Feb 28, 2024

[TS migration] Migrate 'SettingsInitial' page to TypeScript #36415

[TS migration] Migrate 'SettingsInitial' page to TypeScript #36415

Conversation

kubabutkiewicz commented Feb 13, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

fabioh8010 commented Feb 15, 2024

fabioh8010 Feb 20, 2024

Choose a reason for hiding this comment

melvin-bot bot commented Feb 21, 2024

allroundexperts commented Feb 23, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

allroundexperts commented Feb 26, 2024

kubabutkiewicz commented Feb 26, 2024

kubabutkiewicz Feb 26, 2024

Choose a reason for hiding this comment

allroundexperts left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Feb 26, 2024

bondydaa left a comment

Choose a reason for hiding this comment

bondydaa Feb 26, 2024

Choose a reason for hiding this comment

OSBotify commented Feb 26, 2024

OSBotify commented Feb 26, 2024

OSBotify commented Feb 28, 2024

kubabutkiewicz commented Feb 13, 2024 •

edited

Loading

allroundexperts commented Feb 23, 2024 •

edited

Loading