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 'AppNavigator' lib to TypeScript #29157

Merged
merged 33 commits into from
Dec 6, 2023

Conversation

VickyStash
Copy link
Contributor

@VickyStash VickyStash commented Oct 10, 2023

Details

[TS migration] Migrate 'AppNavigator' lib to TypeScript

Fixed Issues

$ #24935
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console

Note: Test the app generally, navigating through the app, login screen, settings, report screen, etc

  1. Open the app and log in.
  2. Create a Money Request, and make sure the navigation works as expected.
  3. Open any chat/report.
  4. Open Settings, look through different Settings screens: Profile, Workspaces, Wallet, Preferences, etc and make sure the navigation works as expected.
  5. Log out and log in again. Navigate to a few screens to make sure that the navigator works properly.

Offline tests

N/A

QA Steps

  • Verify that no errors appear in the JS console

Note: Test the app generally, navigating through the app, login screen, settings, report screen, etc

  1. Open the app and log in.
  2. Create a Money Request, and make sure the navigation works as expected.
  3. Open any chat/report.
  4. Open Settings, look through different Settings screens: Profile, Workspaces, Wallet, Preferences, etc and make sure the navigation works as expected.
  5. Log out and log in again. Navigate to a few screens to make sure that the navigator works properly.

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
      • 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
android1.mp4
Android: mWeb Chrome
android_web1.mp4
iOS: Native
ios1.mp4
iOS: mWeb Safari
ios_web1.mp4
MacOS: Chrome / Safari
web1.mp4
MacOS: Desktop
desktop1.mp4

src/libs/Navigation/AppNavigator/AuthScreens.tsx Outdated Show resolved Hide resolved
src/libs/Navigation/AppNavigator/AuthScreens.tsx Outdated Show resolved Hide resolved
src/libs/Navigation/AppNavigator/AuthScreens.tsx Outdated Show resolved Hide resolved
src/libs/Navigation/AppNavigator/AuthScreens.tsx Outdated Show resolved Hide resolved
src/libs/Navigation/AppNavigator/Navigators/Overlay.tsx Outdated Show resolved Hide resolved
src/libs/Navigation/AppNavigator/RHPScreenOptions.ts Outdated Show resolved Hide resolved
src/libs/Navigation/AppNavigator/ReportScreenIDSetter.ts Outdated Show resolved Hide resolved
src/libs/Navigation/Navigation.js Outdated Show resolved Hide resolved
# Conflicts:
#	src/SCREENS.ts
#	src/libs/Navigation/AppNavigator/AuthScreens.tsx
#	src/libs/Navigation/AppNavigator/ModalStackNavigators.js
#	src/libs/Navigation/AppNavigator/Navigators/CentralPaneNavigator.tsx
#	src/libs/Navigation/AppNavigator/Navigators/Overlay.tsx
#	src/libs/Navigation/AppNavigator/Navigators/RightModalNavigator.tsx
#	src/libs/Navigation/AppNavigator/PublicScreens.tsx
#	src/libs/Navigation/AppNavigator/RHPScreenOptions.ts
#	src/libs/Navigation/AppNavigator/ReportScreenIDSetter.ts
#	src/libs/Navigation/AppNavigator/ReportScreenWrapper.js
#	src/libs/Navigation/AppNavigator/createCustomStackNavigator/CustomRouter.ts
#	src/libs/Navigation/AppNavigator/createCustomStackNavigator/index.js
#	src/libs/Navigation/AppNavigator/getRootNavigatorScreenOptions.ts
#	src/libs/Navigation/AppNavigator/index.tsx
#	src/libs/Navigation/AppNavigator/modalCardStyleInterpolator.ts
#	src/styles/cardStyles/types.ts
#	src/types/onyx/Report.ts
# Conflicts:
#	src/SCREENS.ts
#	src/libs/actions/App.ts
# Conflicts:
#	src/SCREENS.ts
#	src/libs/Navigation/AppNavigator/AuthScreens.tsx
#	src/libs/Navigation/AppNavigator/ModalStackNavigators.js
#	src/libs/Navigation/AppNavigator/Navigators/Overlay.tsx
#	src/libs/Navigation/AppNavigator/Navigators/RightModalNavigator.tsx
#	src/libs/Navigation/Navigation.js
#	src/types/onyx/Report.ts
# Conflicts:
#	src/libs/Navigation/AppNavigator/ModalStackNavigators.js
#	src/libs/Navigation/AppNavigator/Navigators/RightModalNavigator.tsx
#	src/libs/Navigation/AppNavigator/RHPScreenOptions.ts
#	src/libs/Navigation/AppNavigator/getRootNavigatorScreenOptions.ts
# Conflicts:
#	src/libs/Navigation/AppNavigator/ReportScreenIDSetter.ts
Copy link
Contributor

@rezkiy37 rezkiy37 left a comment

Choose a reason for hiding this comment

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

Left comments. Overall, LGTM!

src/SCREENS.ts Show resolved Hide resolved
src/SCREENS.ts Show resolved Hide resolved
src/SCREENS.ts Show resolved Hide resolved
src/libs/Navigation/AppNavigator/AuthScreens.tsx Outdated Show resolved Hide resolved
src/pages/ErrorPage/NotFoundPage.js Show resolved Hide resolved
@allroundexperts
Copy link
Contributor

allroundexperts commented Dec 5, 2023

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 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-12-06.at.4.31.32.AM.mov
Android: mWeb Chrome
Screen.Recording.2023-12-06.at.4.30.03.AM.mov
iOS: Native
Screen.Recording.2023-12-06.at.4.28.37.AM.mov
iOS: mWeb Safari
Screen.Recording.2023-12-06.at.4.27.23.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2023-12-06.at.4.17.16.AM.mov
MacOS: Desktop
Screen.Recording.2023-12-06.at.4.24.46.AM.mov

Comment on lines -270 to -275
mode="modal"
// We are disabling the default keyboard handling here since the automatic behavior is to close a
// keyboard that's open when swiping to dismiss a modal. In those cases, pressing the back button on
// a header will briefly open and close the keyboard and crash Android.
// eslint-disable-next-line react/jsx-props-no-multi-spaces
keyboardHandlingEnabled={false}
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this being removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@allroundexperts Please, see this discussion for the context

return getTopMostReportIDFromRHP(topmostRoute.state);
}

if (topmostRoute.params && topmostRoute.params.reportID) {
if (topmostRoute?.params && 'reportID' in topmostRoute.params && typeof topmostRoute.params.reportID === 'string' && topmostRoute.params.reportID) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious why && typeof topmostRoute.params.reportID === 'string' && topmostRoute.params.reportID is needed? Shouldn't 'reportID' in topmostRoute.params be enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@allroundexperts Not really, we need to narrow down the type to make sure reportID is string, that's why

addCentralPaneNavigatorRoute(partialState);
}
const state = stackRouter.getRehydratedState(partialState, {routeNames, routeParamList});
const state = stackRouter.getRehydratedState(partialState, {routeNames, routeParamList, routeGetIdList});
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is routeGetIdList being added here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because routeGetIdList is a required param of RouterConfigOptions.
getRehydratedState typing
RouterConfigOptions typing

@@ -13,7 +13,7 @@ let hasPendingNetworkCheck = false;

// Holds all of the callbacks that need to be triggered when the network reconnects
let callbackID = 0;
const reconnectionCallbacks: Record<string, () => Promise<void>> = {};
const reconnectionCallbacks: Record<string, () => void> = {};
Copy link
Contributor

Choose a reason for hiding this comment

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

Why isn't this a promise anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because the callback passed to reconnect function is not a Promise

NetworkConnection.onReconnect(() => {
if (isLoadingApp) {
App.openApp();
} else {
App.reconnectApp(lastUpdateIDAppliedToClient);
}
});

type GetNavigationModalCardStylesParams = {isSmallScreenWidth: number};

type GetNavigationModalCardStyles = (params: GetNavigationModalCardStylesParams) => ViewStyle;
type GetNavigationModalCardStyles = () => ViewStyle;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why the params are being removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@allroundexperts Because this type is used for typing the functions without params:

const getNavigationModalCardStyles: GetNavigationModalCardStyles = () => ({

const getNavigationModalCardStyles: GetNavigationModalCardStyles = () => ({

const getNavigationModalCardStyles: GetNavigationModalCardStyles = () => ({

Comment on lines +97 to +99
/** If the admin room should be opened */
openOnAdminRoom?: boolean;

Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this being added?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Without it we will have next TS error in ReportScreenIDSetter.ts file
image

@allroundexperts
Copy link
Contributor

Found the following two console warnings. I'm quite sure that these are not related to this PR but still, it would be good to confirm these before merging @VickyStash!

Screenshot 2023-12-06 at 4 37 45 AM Screenshot 2023-12-06 at 4 37 33 AM

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.

Tests well. I'm not blocking the approval because of my comments because this is such a high priority PR.

Copy link

melvin-bot bot commented Dec 5, 2023

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

@melvin-bot melvin-bot bot requested a review from Gonals December 5, 2023 23:40
@VickyStash
Copy link
Contributor Author

@allroundexperts I wasn't able to reproduce a console warning from the first screenshot, do you remember the steps of reproduction?
Regarding the second one, I see the same warning on the main branch so it's not related to this PR

@VickyStash
Copy link
Contributor Author

@Gonals The SWM team is currently working on navigation refactoring, and this migration could speed up things - so please prioritize this one 🙏

Gonals
Gonals previously approved these changes Dec 6, 2023
Copy link
Contributor

@Gonals Gonals left a comment

Choose a reason for hiding this comment

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

This looks good to me and all comments have been answered.

@Gonals
Copy link
Contributor

Gonals commented Dec 6, 2023

Ahh, damn. @VickyStash, seems like we have some conflicts. I'll merge once they are solved

# Conflicts:
#	src/libs/Navigation/AppNavigator/createCustomStackNavigator/CustomRouter.ts
@VickyStash
Copy link
Contributor Author

@Gonals Is there anything that prevents you from merging? 😅

@Gonals Gonals merged commit bbe73ef into Expensify:main Dec 6, 2023
16 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Dec 6, 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

OSBotify commented Dec 6, 2023

🚀 Deployed to staging by https://github.com/Gonals in version: 1.4.9-0 🚀

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

1 similar comment
@OSBotify
Copy link
Contributor

OSBotify commented Dec 6, 2023

🚀 Deployed to staging by https://github.com/Gonals in version: 1.4.9-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Dec 8, 2023

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.9-5 🚀

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.

9 participants