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 'OptionsListUtils.js' lib to TypeScript #32470

Merged

Conversation

kubabutkiewicz
Copy link
Contributor

@kubabutkiewicz kubabutkiewicz commented Dec 5, 2023

Details

Fixed Issues

$ #24921

Tests

  1. Click on Search icon
  2. Check if you are able to search for users and select
  3. Make a Money Request
  4. Check if you are able to search for users
  5. Go to Workspace Settings
  6. Go to Members
  7. Invite users to Workspace
  8. Create a Room
  9. Invite users to Room
  • 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: 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 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.mp4
Android: mWeb Chrome
mchrome.mp4
iOS: Native
ios.mp4
iOS: mWeb Safari
msafari.mp4
MacOS: Chrome / Safari
web.mp4
MacOS: Desktop
desktop.mp4

src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/libs/OptionsListUtils.ts Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/libs/OptionsListUtils.ts Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
src/types/onyx/IOU.ts Outdated Show resolved Hide resolved
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.

forgot these ones

src/libs/OptionsListUtils.ts Show resolved Hide resolved
src/libs/OptionsListUtils.ts Outdated Show resolved Hide resolved
@kubabutkiewicz
Copy link
Contributor Author

@getusha Done!

Copy link

melvin-bot bot commented Jan 25, 2024

We did not find an internal engineer to review this PR, trying to assign a random engineer to #24921 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 deetergp January 25, 2024 13:06
Copy link
Contributor

@deetergp deetergp left a comment

Choose a reason for hiding this comment

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

Looks good and tests well. Thanks!

@deetergp deetergp merged commit ac94dc5 into Expensify:main Jan 25, 2024
17 checks passed
Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

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

TS check failing on latest main. Seems like came from this PR

Screenshot 2024-01-26 at 4 43 08 AM

const personalDetailList = _.values(personalDetailMap);
const personalDetail = personalDetailList[0] || {};
const personalDetailList = Object.values(personalDetailMap).filter((details): details is PersonalDetails => !!details);
const personalDetail = personalDetailList[0];
Copy link
Contributor

@ntdiary ntdiary Jan 26, 2024

Choose a reason for hiding this comment

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

Hi, @kubabutkiewicz, personalDetail might be undefined, and this could lead to a crash when later code attempts to access personalDetail.login later.

result.alternateText = showChatPreviewLine && lastMessageText ? lastMessageText : LocalePhoneNumber.formatPhoneNumber(personalDetail.login ?? '');

reportName = ReportUtils.getDisplayNameForParticipant(accountIDs[0]) || LocalePhoneNumber.formatPhoneNumber(personalDetail.login ?? '');

Copy link
Contributor

@abzokhattab abzokhattab Jan 26, 2024

Choose a reason for hiding this comment

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

@ntdiary agree .. it's failing in the new/chat page in my account we need to change it to personalDetail?.login in all occurrences

cc @deetergp

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @ntdiary !
I think this

const personalDetailList = Object.values(personalDetailMap).filter((details): details is PersonalDetails => !!details);
is filterning falsy values from personalDetailList right? so personalDetail should always be defined in my opinion.
Is the crash already happend, or this was just a assumption?

Copy link
Contributor

@ntdiary ntdiary Jan 26, 2024

Choose a reason for hiding this comment

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

Yeah, it did happen. 😂

It seems that accountIDs might be an empty array.

test.mp4

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hmm its weird because I even run this is TS playground and it should filter those falsy values
image
but yeah I will make a PR with a fix.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ntdiary do you know if there is an issue for that created?

Copy link
Contributor

Choose a reason for hiding this comment

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

@ntdiary do you know if there is an issue for that created?

I'm not sure if there is a created issue, I just happened to encounter this error while reviewing another PR #32665, so I left a comment here. 😂

Copy link
Contributor

Choose a reason for hiding this comment

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

Let's fix this asap. This blocks testing important parts of the app.
This happens because const personalDetailMap = getPersonalDetailsForAccountIDs(accountIDs, personalDetails); can be empty json {}

Screen.Recording.2024-01-28.at.9.05.49.PM.mov

} else if (ReportUtils.isReportMessageAttachment({text: report.lastMessageText, html: report.lastMessageHtml, translationKey: report.lastMessageTranslationKey})) {
lastMessageTextFromReport = `[${Localize.translateLocal(report.lastMessageTranslationKey || 'common.attachment')}]`;
} else if (ReportUtils.isReportMessageAttachment({text: report?.lastMessageText ?? '', html: report?.lastMessageHtml, translationKey: report?.lastMessageTranslationKey, type: ''})) {
lastMessageTextFromReport = `[${Localize.translateLocal((report?.lastMessageTranslationKey ?? 'common.attachment') as TranslationPaths)}]`;
Copy link
Contributor

Choose a reason for hiding this comment

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

This caused regression. We should keep ||

BUG: Crash on LHN for non-expensify email domain, [MISSING TRNSLATION] for expensify domain
[Attachment] is the expected string

Screenshot 2024-01-28 at 10 58 29 PM Screenshot 2024-01-28 at 10 58 10 PM Screenshot 2024-01-28 at 11 01 08 PM

Repro step: send any attachment to any chat on iOS app

@getusha
Copy link
Contributor

getusha commented Jan 29, 2024

@kubabutkiewicz Should we revert this or fix the raised regressions.

@kubabutkiewicz
Copy link
Contributor Author

I am publishing the fix now

@kubabutkiewicz
Copy link
Contributor Author

PR: #35300 @getusha @situchan
I dont see any issues created for those regressions yet

@situchan
Copy link
Contributor

I dont see any issues created for those regressions yet

That's because this PR didn't hit staging yet. Only QA team is reporting bugs. Not contributors

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/deetergp in version: 1.4.33-0 🚀

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

.map((tag) => ({name: tag, enabled: true}));
const filteredTags = enabledTags.filter((tag) => !selectedOptionNames.includes(tag.name));

if (selectedOptions) {
Copy link
Contributor

@situchan situchan Jan 30, 2024

Choose a reason for hiding this comment

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

This caused regression. selectedOptions is array and always truthy.
Should be selectedOptions.length.
Issue created for this: #35423

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.33-5 🚀

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

if (name) {
const categoryObject: Category = {
name,
enabled: categories[name].enabled ?? false,
Copy link
Contributor

Choose a reason for hiding this comment

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

Category should have been accessed safely, rare case where categories[name] is undefined. ref: #36622

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.