Replace with correct path in nested state by c3024 · Pull Request #51071 · Expensify/App

c3024 · 2024-10-18T07:03:24Z

Details

When we replace a relative path URL in a nested state and it becomes inconsistent with the browser history path, the browser history goes back once more, inserting a relative path in the URL and deforming it. This PR fixes it.

Fixed Issues

$ #49854
PROPOSAL: #49854 (comment)

Tests

1.	Log on to ND.
2.	Create a workspace if one does not already exist.
3.	Click on “Settings” in the bottom tab bar > “Workspaces” > Click on a workspace > “Members.”
4.	Click the browser/device back button.
5.	Click on “Members” again.
6.	Click the browser/device back button again.
7.	Verify that the “Not found” page does not appear and it correctly navigates to the workspace’s initial page.

Verify that no errors appear in the JS console

Offline tests

1.	Log on to ND.
2.	Create a workspace if one does not already exist.
3.      Go offline.
4.	Click on “Settings” in the bottom tab bar > “Workspaces” > Click on a workspace > “Members.”
5.	Click the browser/device back button.
6.	Click on “Members” again.
7.	Click the browser/device back button again.
8.	Verify that the “Not found” page does not appear and it correctly navigates to the workspace’s initial page.

QA Steps

1.	Log on to ND.
2.	Create a workspace if one does not already exist.
3.	Click on “Settings” in the bottom tab bar > “Workspaces” > Click on a workspace > “Members.”
4.	Click the browser/device back button.
5.	Click on “Members” again.
6.	Click the browser/device back button again.
7.	Verify that the “Not found” page does not appear and it correctly navigates to the workspace’s initial page.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

urlAndroid.mp4

Android: mWeb Chrome

urlAndroidmWeb.mp4

iOS: Native

urliOS.mp4

iOS: mWeb Safari

urliOSmWeb.mp4

MacOS: Chrome / Safari

urlChrome.mp4

urlChromeNarrow.mp4

MacOS: Desktop

urlDesktop.mp4

urlDesktopNarrow.mp4

melvin-bot · 2024-10-18T08:23:08Z

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

ntdiary · 2024-10-21T09:40:34Z

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

51071-android-native.mp4

Android: mWeb Chrome

51071-android-web.mp4

iOS: Native

51071-ios-native.mp4

iOS: mWeb Safari

51071-ios-safari.mp4

MacOS: Chrome / Safari

51071-web.mp4

MacOS: Desktop

51071-desktop.mp4

ntdiary

LGTM. :)

marcochavezf

Thanks!

melvin-bot · 2024-10-21T16:54:09Z

@marcochavezf 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.

marcochavezf · 2024-10-21T16:57:37Z

The checks were passing and the author PR checklist is completed. Removing the Emergency label

OSBotify · 2024-10-21T17:04:41Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2024-10-22T04:49:09Z

🚀 Deployed to staging by https://github.com/marcochavezf in version: 9.0.52-0 🚀

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

github-actions · 2024-10-23T16:26:36Z

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

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

replace correct path in nested state

a79f5d5

c3024 marked this pull request as ready for review October 18, 2024 08:23

c3024 requested a review from a team as a code owner October 18, 2024 08:23

melvin-bot Bot requested a review from ntdiary October 18, 2024 08:23

melvin-bot Bot removed the request for review from a team October 18, 2024 08:23

ntdiary approved these changes Oct 21, 2024

View reviewed changes

melvin-bot Bot requested a review from marcochavezf October 21, 2024 10:30

marcochavezf approved these changes Oct 21, 2024

View reviewed changes

marcochavezf merged commit 16e3620 into Expensify:main Oct 21, 2024

melvin-bot Bot added the Emergency label Oct 21, 2024

marcochavezf removed the Emergency label Oct 21, 2024

github-actions Bot mentioned this pull request Oct 22, 2024

Deploy Checklist: New Expensify 2024-10-22 #51219

Closed

74 tasks done

melvin-bot Bot mentioned this pull request Oct 23, 2024

[HOLD for payment 2024-10-30] [$250] mWeb - Workspace - Opens "Hmm it's not here" when tapping system back button #49854

Closed

1 of 6 tasks

Navigation Menu

Repository navigation

Replace with correct path in nested state - #51071

Replace with correct path in nested state#51071
marcochavezf merged 1 commit into
Expensify:mainfrom
c3024:replace-correct-path-in-nested-state

c3024 commented Oct 18, 2024 •

edited

Loading

Uh oh!

melvin-bot Bot commented Oct 18, 2024

Uh oh!

ntdiary commented Oct 21, 2024 •

edited

Loading

Uh oh!

ntdiary left a comment

Uh oh!

marcochavezf left a comment

Uh oh!

melvin-bot Bot commented Oct 21, 2024

Uh oh!

marcochavezf commented Oct 21, 2024

Uh oh!

OSBotify commented Oct 21, 2024

Uh oh!

github-actions Bot commented Oct 22, 2024

Uh oh!

github-actions Bot commented Oct 23, 2024

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

c3024 commented Oct 18, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Oct 18, 2024

Uh oh!

ntdiary commented Oct 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

ntdiary left a comment

Choose a reason for hiding this comment

Uh oh!

marcochavezf left a comment

Choose a reason for hiding this comment

Uh oh!

melvin-bot Bot commented Oct 21, 2024

Uh oh!

marcochavezf commented Oct 21, 2024

Uh oh!

OSBotify commented Oct 21, 2024

Uh oh!

github-actions Bot commented Oct 22, 2024

Uh oh!

github-actions Bot commented Oct 23, 2024

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

c3024 commented Oct 18, 2024 •

edited

Loading

ntdiary commented Oct 21, 2024 •

edited

Loading