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 'Desktop' files to TypeScript #37615

Merged
merged 8 commits into from
Mar 15, 2024

Conversation

VickyStash
Copy link
Contributor

@VickyStash VickyStash commented Mar 1, 2024

Details

[TS migration] Migrate 'Desktop' files to TypeScript

Fixed Issues

$ #25333
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console
  1. Delete old desktop/dist folder
  2. Launch desktop app
  3. Login and check some basic user operations (send a message, create a money request, create a task)
  4. Check that top menu looks as expected and test several flows from there. (for example History -> Back/Forward)
  5. Open any chat and right click on composer (input). Make sure the shown menu looks okay.

Since concurrently lib got updated in this PR, please also check that next scripts work as expected:

  • npm run ipdad
  • npm run ipad-sm
  • npm run web

Offline tests

N/A

QA Steps

  • Verify that no errors appear in the JS console
  1. Launch desktop app
  2. Login and check some basic user operations (send a message, create a money request, create a task)
  3. Check that top menu looks as expected and test several flows from there. (for example History -> Back/Forward)
  4. Open any chat and right click on composer (input). Make sure the shown menu looks okay.

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

MacOS: Desktop
desktop1.mp4

desktop/start.ts Outdated Show resolved Hide resolved
desktop/start.ts Outdated Show resolved Hide resolved
return contextMenu({
labels: {
cut: Localize.translate(preferredLocale, 'desktopApplicationMenu.cut'),
paste: Localize.translate(preferredLocale, 'desktopApplicationMenu.paste'),
copy: Localize.translate(preferredLocale, 'desktopApplicationMenu.copy'),
},
append: (defaultActions, parameters, browserWindow) => [
new MenuItem({
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've made this update cause append function expects to return an array of MenuItemConstructorOptions. It seems to work as expected.
image

Comment on lines -299 to -300
details.requestHeaders.origin = CONFIG.EXPENSIFY.URL_EXPENSIFY_CASH;
details.requestHeaders.referer = CONFIG.EXPENSIFY.URL_EXPENSIFY_CASH;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

URL_EXPENSIFY_CASH was removed from config a lot of time ago.

@@ -404,14 +413,13 @@ const mainWindow = () => {
submenu: [
{
id: 'back',
role: 'back',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

back role doesn't exist, and overall since the menu item has click function it wasn't necessary. See more in docs

@@ -420,14 +428,13 @@ const mainWindow = () => {
},
{
id: 'forward',
role: 'forward',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

forward role doesn't exist, and overall since the menu item has click function it wasn't necessary. See more in docs

accelerator: process.platform === 'darwin' ? 'Cmd+[' : 'Shift+[',
click: () => {
browserWindow.webContents.goBack();
},
},
{
role: 'back',
label: 'backWithKeyShortcut',
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 role/label this item made the app crash, since 'back' role doesn't exist I've added a label, it's not shown since this item is not visible.

accelerator: process.platform === 'darwin' ? 'Cmd+]' : 'Shift+]',
click: () => {
browserWindow.webContents.goForward();
},
},
{
role: 'forward',
label: 'forwardWithKeyShortcut',
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 role/label this item made the app crash, since 'back' role doesn't exist I've added a label, it's not shown since this item is not visible.

desktop/start.ts Outdated Show resolved Hide resolved
desktop/contextBridge.ts Outdated Show resolved Hide resolved
desktop/contextBridge.ts Outdated Show resolved Hide resolved
@VickyStash
Copy link
Contributor Author

I haven't updated contextBridge.js extension here and here, cause in this cases it relates to dist/contextBridge.js file and updates are causing crashes.

Copy link
Contributor

@fabioh8010 fabioh8010 left a comment

Choose a reason for hiding this comment

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

LGTM ❤️ Please test it extensively to make sure desktop apps are running smoothly and the desktop build script too!

Copy link
Contributor

@blazejkustra blazejkustra left a comment

Choose a reason for hiding this comment

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

LGTM! Let's test desktop extensively by QA team 😄

@VickyStash VickyStash marked this pull request as ready for review March 8, 2024 09:24
@VickyStash VickyStash requested a review from a team as a code owner March 8, 2024 09:24
@melvin-bot melvin-bot bot requested review from getusha and removed request for a team March 8, 2024 09:24
Copy link

melvin-bot bot commented Mar 8, 2024

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

@VickyStash
Copy link
Contributor Author

VickyStash commented Mar 8, 2024

@mountiny Could you please generate adhoc builds for this branch to make sure desktop app build is okay?

This comment has been minimized.

@mountiny
Copy link
Contributor

mountiny commented Mar 8, 2024

Seems like it failed in the setupNode step https://github.com/Expensify/App/actions/runs/8206513618/job/22445894155

@mountiny
Copy link
Contributor

mountiny commented Mar 8, 2024

Testing again https://github.com/Expensify/App/actions/runs/8208509429

Does it maybe need to be build off this branch code too?

Copy link
Contributor

github-actions bot commented Mar 8, 2024

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖 iOS 🍎
❌ FAILED ❌ https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/37615/index.html
The QR code can't be generated, because the android build failed iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/37615/NewExpensify.dmg https://37615.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@VickyStash
Copy link
Contributor Author

Does it maybe need to be build off this branch code too?

@mountiny Could you please clarify what do you mean?
I've also tested building locally (build .dmg file and tested it), just in case you mean it 😅

@mountiny
Copy link
Contributor

@VickyStash ah sorry, that was irrelevant after the second build succeeded

Basically what I meant is whether the build workflow uses the config files from the branch it building or from main.

@VickyStash
Copy link
Contributor Author

@getusha kind bump 🙂

@getusha
Copy link
Contributor

getusha commented Mar 14, 2024

@VickyStash not sure if this is related #exfy-roadmap is not opening for me, the skeleton just flickers.

Screen.Recording.2024-03-14.at.1.57.28.in.the.afternoon.mov

@getusha
Copy link
Contributor

getusha commented Mar 14, 2024

@VickyStash noticed a strange thing, after running npm run desktop the web server is also started?

Screenshot 2024-03-14 at 2 08 57 in the afternoon

Screenshot 2024-03-14 at 2 09 46 in the afternoon

@VickyStash
Copy link
Contributor Author

@getusha

#exfy-roadmap is not opening for me, the skeleton just flickers

I think it's related to this issue

@VickyStash
Copy link
Contributor Author

@VickyStash noticed a strange thing, after running npm run desktop the web server is also started?

@getusha It works the same way on the main branch for me, could you confirm?

@getusha
Copy link
Contributor

getusha commented Mar 14, 2024

Can confirm it is the same on main 👍

@getusha
Copy link
Contributor

getusha commented Mar 14, 2024

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design 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

Screenshot 2024-03-14 at 5 20 58 in the afternoon

Android: mWeb Chrome

Screenshot 2024-03-14 at 5 24 02 in the afternoon

iOS: Native

Uploading Screenshot 2024-03-14 at 5.24.29 in the afternoon.png…

iOS: mWeb Safari

Screenshot 2024-03-14 at 5 21 58 in the afternoon

MacOS: Chrome / Safari

Screenshot 2024-03-14 at 5 20 02 in the afternoon

MacOS: Desktop
Screen.Recording.2024-03-14.at.3.01.06.in.the.afternoon.mov

Copy link

melvin-bot bot commented Mar 14, 2024

We did not find an internal engineer to review this PR, trying to assign a random engineer to #25333 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 mountiny March 14, 2024 15:07
mountiny
mountiny previously approved these changes Mar 15, 2024
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.

Looks fine to me, thanks for testing thoroughly, be on a look out if there will be any issues with desktop please

@mountiny mountiny merged commit cdd93d1 into Expensify:main Mar 15, 2024
18 checks passed
Copy link

melvin-bot bot commented Mar 15, 2024

@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@mountiny
Copy link
Contributor

Hmm tests were passing

@OSBotify
Copy link
Contributor

✋ 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.54-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.4.54-4 🚀

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

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

Successfully merging this pull request may close these issues.

6 participants