Fix/34610: Remove NewDistanceRequestPage and EditRequestDistancePage

[DylanDylann]

Details

Use IOURequestStepDistance instead of NewDistanceRequestPage and EditRequestDistancePage

Fixed Issues

$ #34610
PROPOSAL: #34610 (comment)

Tests

1. Create a new distance request
2. While creating a new request click on the distance field
3. Verify that the route display /create/request/ (only apply this step on web)
4. After creating distance request click on distance field to edit
5. Verify that the route display /edit/request/ (only apply this step on web)
6. Verify that everything works well as before

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Create a new distance request
2. While creating a new request click on the distance field
3. Verify that the route display /create/request/ (only apply this step on web)
4. After creating distance request click on distance field to edit
5. Verify that the route display /edit/request/ (only apply this step on web)
6. Verify that everything works well as before

• 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

Screen.Recording.2024-03-20.at.11.12.37.mov

Android: mWeb Chrome

Screen.Recording.2024-03-20.at.10.52.25.mov

iOS: Native

Screen.Recording.2024-03-20.at.11.09.39.mov

iOS: mWeb Safari

Screen.Recording.2024-03-20.at.10.51.33.mov

MacOS: Chrome / Safari

Screen.Recording.2024-03-20.at.10.46.08.mp4

MacOS: Desktop

Screen.Recording.2024-03-20.at.10.53.37.mov

[melvin-bot]

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

[jakub-trzebiatowski]

Linter complaining

[jakub-trzebiatowski]

Once you fix the lints, would you please very briefly sum up what changed since the un-holding?

[DylanDylann]

@cubuspl42 Currently, we use IOURequestStepDistance to create and edit distance. We will use action from the route to determine the user's current action (create or edit). Then applying suitable logic for each action

[DylanDylann]

@cubuspl42 The PR is ready for review

[jakub-trzebiatowski]

Verify that the route display /create/request/

This doesn't apply to Native. Please make the testing steps cover all platforms. If some platforms are meant to be unaffected, describe tests that verify that.

[jakub-trzebiatowski]

Verify that the route display /create/request/

Also, I assume you mean that the "browser's URL should update to", "route display(s)" is not a common way to phrase that.

[DylanDylann]

@cubuspl42

This doesn't apply to Native. Please make the testing steps cover all platforms. If some platforms are meant to be unaffected, describe tests that verify that.

This change is so straightforward. Verifying the route on the web is enough. In other platforms, ensuring the distance request works well is enough

[DylanDylann]

@cubuspl42

Also, I assume you mean that the "browser's URL should update to", "route display(s)" is not a common way to phrase that.

I think it is a good way to verify this PR. we need to make sure the new route is applied instead of the old one

[jakub-trzebiatowski]

@cubuspl42

Also, I assume you mean that the "browser's URL should update to", "route display(s)" is not a common way to phrase that.

I think it is a good way to verify this PR. we need to make sure the new route is applied instead of the old one

I'm not discussing the essence of what you wrote. I'm just leaving an organizational comment. Unless tests are cross platform, mention it. Per single step, or per set of steps.

So if you want to comment on things like URL bar or any Web-specific behavior, say "On the Web, expect that the URL is...".

If a whole set of steps is for a single platform only, you can write:

On Native:

• something
• something
• something

On Web:

• Ensure that flow XYZ is fully functional

[DylanDylann]

@cubuspl42 Thanks for your reminder

Updated:

1. Create a new distance request
2. While creating a new request click on the distance field
3. Verify that the route display /create/request/ (only apply this step on web)
4. After creating distance request click on distance field to edit
5. Verify that the route display /edit/request/ (only apply this step on web)
6. Verify that everything works well as before

[jakub-trzebiatowski]

I think there's no reason to skip QA; let's move Tests to QA Steps and write "Same as QA Steps" in "Tests"

[jakub-trzebiatowski]

@cubuspl42

Also, I assume you mean that the "browser's URL should update to", "route display(s)" is not a common way to phrase that.

I think it is a good way to verify this PR. we need to make sure the new route is applied instead of the old one

I'm not sure I completely understand you. Do you mean that the verification you mention is taking a look at the browser's URL bar, or not?

[jakub-trzebiatowski]

I'm observing some exceptions, I'm not sure what's the root cause. Might be something on main.

I tested after merging in main (51ef6c1bd1cd3d981db744bff1fcff9e7c670c0c).

remove-NewDistanceRequestPage-ios-compressed.mp4

[DylanDylann]

I'm not sure I completely understand you. Do you mean that the verification you mention is taking a look at the browser's URL bar, or not?

Yeah, the browser's URL bar. It is my mean

[DylanDylann]

@cubuspl42 Please ping me if there is any problem. We should speed up this PR

[jakub-trzebiatowski]

@DylanDylann I had problems testing this yesterday (like I mentioned), but I'm trying again.

[DylanDylann]

@cubuspl42 I have never seen this error while testing. Please log out and log in again to reset ONYX.

[jakub-trzebiatowski]

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

remove-NewDistanceRequestPage-android-compressed.mp4

Android: mWeb Chrome

remove-NewDistanceRequestPage-android-web-compressed.mp4

iOS: Native

remove-NewDistanceRequestPage-ios-compressed.mp4

iOS: mWeb Safari

remove-NewDistanceRequestPage-ios-web-compressed.mp4

MacOS: Chrome / Safari

remove-NewDistanceRequestPage-web-converted.mp4

MacOS: Desktop

[cristipaval]

Thanks for working on this!

[cristipaval]

Thanks for working on this!

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.4.56-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.56-8 🚀

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