[No QA] [TS migration] Migrate 'ValidationUtils.js' lib to TypeScript #27846

kubabutkiewicz · 2023-09-20T09:26:33Z

Details

Fixed Issues

$ 24888

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

web.mp4

Mobile Web - Chrome

Mobile Web - Safari

Desktop

desktop.mp4

iOS

ios.mp4

Android

android.mp4

src/libs/ValidationUtils.ts

rezkiy37

Left a couple comments.

src/libs/ValidationUtils.ts

rezkiy37

LGTM

melvin-bot · 2023-09-22T15:49:45Z

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

joelbettner · 2023-09-25T04:15:49Z

@thiagobrez @kubabutkiewicz could one of you do the checklist, please?

fabioh8010 · 2023-09-25T08:29:03Z

@joelbettner Because this PR is from CK, SWM engineers will make the checklist for us.

joelbettner · 2023-09-25T09:10:14Z

@kubabutkiewicz can you make sure the checklist gets done. Thanks!

blazejkustra

LGTM, SWM still need to do the checklist.

blazejkustra · 2023-09-26T06:42:51Z

Working on the checklist...

blazejkustra · 2023-09-26T12:30:42Z

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

web.mov

Mobile Web - Chrome

a-web.mov

Mobile Web - Safari

i-web.mov

Desktop

desktop.mov

iOS

ios.mov

Android

android.mov

situchan · 2023-09-27T12:35:01Z

src/libs/ValidationUtils.ts

-function isExistingRoomName(roomName, reports, policyID) {
-    return _.some(reports, (report) => report && report.policyID === policyID && report.reportName === roomName);
+function isExistingRoomName(roomName: string, reports: Report[], policyID: string): boolean {
+    return reports.some((report) => report && report.policyID === policyID && report.reportName === roomName);


This causes regression. App crashes when type something on room name input field. Shall I raise quick PR fixing that?

Screen.Recording.2023-09-27.at.6.32.44.PM.mov

I went ahead and created follow-up PR since this is critical bug.
@joelbettner can you please review?

OSBotify · 2023-09-28T19:17:46Z

🚀 Deployed to staging by https://github.com/joelbettner in version: 1.3.75-0 🚀

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

OSBotify · 2023-10-02T17:21:41Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.75-12 🚀

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

OSBotify · 2023-10-02T17:50:19Z

🚀 Deployed to staging by https://github.com/joelbettner in version: 1.3.76-0 🚀

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

OSBotify · 2023-10-03T15:51:16Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.76-6 🚀

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

kubabutkiewicz added 4 commits September 20, 2023 11:08

ref: move ValidationUtils lib to TS

cd18d7c

fix: fixed problem

d38fdd5

fix: last typescript error

1ae53c8

Merge branch 'main' into ts-migration/ValidationUtils-lib

6cb03a6

rezkiy37 reviewed Sep 21, 2023

View reviewed changes

src/libs/ValidationUtils.ts Outdated Show resolved Hide resolved

rezkiy37 reviewed Sep 21, 2023

View reviewed changes

src/libs/ValidationUtils.ts Outdated Show resolved Hide resolved

rezkiy37 reviewed Sep 21, 2023

View reviewed changes

fix: resolve comments

38e537d

thiagobrez reviewed Sep 21, 2023

View reviewed changes

src/libs/ValidationUtils.ts Show resolved Hide resolved

thiagobrez reviewed Sep 21, 2023

View reviewed changes

src/libs/ValidationUtils.ts Show resolved Hide resolved

fabioh8010 reviewed Sep 21, 2023

View reviewed changes

src/libs/ValidationUtils.ts Outdated Show resolved Hide resolved

fix: resolve comments

10a8e7e

fabioh8010 approved these changes Sep 22, 2023

View reviewed changes

rezkiy37 reviewed Sep 22, 2023

View reviewed changes

kubabutkiewicz marked this pull request as ready for review September 22, 2023 15:49

kubabutkiewicz requested a review from a team as a code owner September 22, 2023 15:49

melvin-bot bot requested review from joelbettner and removed request for a team September 22, 2023 15:49

blazejkustra approved these changes Sep 25, 2023

View reviewed changes

joelbettner approved these changes Sep 27, 2023

View reviewed changes

joelbettner merged commit 3e78070 into Expensify:main Sep 27, 2023
1 of 2 checks passed

situchan reviewed Sep 27, 2023

View reviewed changes

situchan mentioned this pull request Sep 28, 2023

[CP Staging] fix crash on room name validation #28366

Merged

58 tasks

OSBotify mentioned this pull request Sep 28, 2023

Deploy Checklist: New Expensify 2023-09-28 #28412

Closed

OSBotify mentioned this pull request Oct 2, 2023

Deploy Checklist: New Expensify 2023-10-02 #28635

Closed

situchan mentioned this pull request Oct 9, 2023

[HOLD for payment 2023-10-10] [HOLD for payment 2023-10-09] Room - App crashes when typing room name during room creation #28463

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA] [TS migration] Migrate 'ValidationUtils.js' lib to TypeScript #27846

[No QA] [TS migration] Migrate 'ValidationUtils.js' lib to TypeScript #27846

kubabutkiewicz commented Sep 20, 2023 •

edited

Loading

rezkiy37 left a comment

rezkiy37 left a comment

melvin-bot bot commented Sep 22, 2023

joelbettner commented Sep 25, 2023

fabioh8010 commented Sep 25, 2023

joelbettner commented Sep 25, 2023

blazejkustra left a comment

blazejkustra commented Sep 26, 2023

blazejkustra commented Sep 26, 2023

situchan Sep 27, 2023 •

edited

Loading

situchan Sep 28, 2023 •

edited

Loading

OSBotify commented Sep 28, 2023

OSBotify commented Oct 2, 2023

OSBotify commented Oct 2, 2023

OSBotify commented Oct 3, 2023

[No QA] [TS migration] Migrate 'ValidationUtils.js' lib to TypeScript #27846

[No QA] [TS migration] Migrate 'ValidationUtils.js' lib to TypeScript #27846

Conversation

kubabutkiewicz commented Sep 20, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

rezkiy37 left a comment

Choose a reason for hiding this comment

rezkiy37 left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Sep 22, 2023

joelbettner commented Sep 25, 2023

fabioh8010 commented Sep 25, 2023

joelbettner commented Sep 25, 2023

blazejkustra left a comment

Choose a reason for hiding this comment

blazejkustra commented Sep 26, 2023

blazejkustra commented Sep 26, 2023

Reviewer Checklist

Screenshots/Videos

situchan Sep 27, 2023 • edited Loading

Choose a reason for hiding this comment

situchan Sep 28, 2023 • edited Loading

Choose a reason for hiding this comment

OSBotify commented Sep 28, 2023

OSBotify commented Oct 2, 2023

OSBotify commented Oct 2, 2023

OSBotify commented Oct 3, 2023

kubabutkiewicz commented Sep 20, 2023 •

edited

Loading

situchan Sep 27, 2023 •

edited

Loading

situchan Sep 28, 2023 •

edited

Loading