fix: Room - No animation when returning to room settings after saving new room description. by Krishna2323 · Pull Request #54623 · Expensify/App

Krishna2323 · 2024-12-27T14:26:00Z

Explanation of Change

Fixed Issues

$ #53153
PROPOSAL: #53153 (comment)

Tests

Navigate to the invoice room or any other room
Click on the header
Select the room description
Enter new description and click on Save
Verify the animation is smooth
Select the room name
Enter new description and click on Save
Verify the animation is smooth

Verify that no errors appear in the JS console

Offline tests

Navigate to the invoice room or any other room
Click on the header
Select the room description
Enter new description and click on Save
Verify the animation is smooth
Select the room name
Enter new description and click on Save
Verify the animation is smooth

QA Steps

Navigate to the invoice room or any other room
Click on the header
Select the room description
Enter new description and click on Save
Verify the animation is smooth
Select the room name
Enter new description and click on Save
Verify the animation is smooth

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android_native.mp4

Android: mWeb Chrome

android_chrome.mp4

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

web_chrome.mp4

MacOS: Desktop

desktop_app.mp4

… new room description. Signed-off-by: krishna2323 <belivethatkg@gmail.com>

melvin-bot · 2024-12-27T14:26:05Z

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

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Pujan92 · 2024-12-30T11:54:21Z

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-01-08.at.22.18.33.mov

MacOS: Desktop

Pujan92 · 2024-12-30T11:56:24Z

    return (
        <AccessOrNotFoundWrapper
-            policyID={policy?.id ?? '-1'}
+            policyID={policy?.id}


Why are we applying changes that don't look related to our issue?

https://github.com/Expensify/App/blob/main/contributingGuides/STYLE.md#default-value-for-inexistent-ids

I updated it because now we can't use default string values as fallback, please refer to the above link.

Pujan92

LGTM!

OSBotify · 2025-01-08T21:03:40Z

✋ 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 · 2025-01-10T03:57:40Z

🚀 Deployed to staging by https://github.com/jasperhuangg in version: 9.0.83-0 🚀

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

github-actions · 2025-01-11T03:25:26Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.83-5 🚀

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

github-actions · 2025-01-13T13:58:47Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.83-5 🚀

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

c3024 · 2025-04-10T11:39:09Z

-    const reportID = report?.reportID ?? '';
+    const reportID = report?.reportID;
    const isUpdatingExistingReport = !!reportID;
+    const [groupChatDraft] = useOnyx(ONYXKEYS.NEW_GROUP_CHAT_DRAFT);


useOnyx does not delay the page till this value is loaded. So, if this page is refreshed, the initial value is undefined and the default value for the input becomes an unexpected value. More details here #58967

fix: Room - No animation when returning to room settings after saving…

d3af8b5

… new room description. Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Krishna2323 requested a review from a team as a code owner December 27, 2024 14:26

melvin-bot Bot requested a review from Pujan92 December 27, 2024 14:26

melvin-bot Bot removed the request for review from a team December 27, 2024 14:26

Krishna2323 added 3 commits December 27, 2024 20:19

fix eslint.

99f1873

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

fix eslint.

4fcb112

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

migrate GroupChatNameEditPage to use useOnyx.

1cbc988

Signed-off-by: krishna2323 <belivethatkg@gmail.com>

Pujan92 reviewed Dec 30, 2024

View reviewed changes

Pujan92 approved these changes Jan 8, 2025

View reviewed changes

melvin-bot Bot requested a review from jasperhuangg January 8, 2025 16:56

jasperhuangg approved these changes Jan 8, 2025

View reviewed changes

jasperhuangg merged commit 1b244b3 into Expensify:main Jan 8, 2025

github-actions Bot mentioned this pull request Jan 10, 2025

Deploy Checklist: New Expensify 2025-01-10 #55051

Closed

54 tasks done

melvin-bot Bot mentioned this pull request Jan 11, 2025

[HOLD for payment 2025-01-18] [$250] Room - No animation when returning to room settings after saving new room description #53153

Closed

1 of 8 tasks

c3024 reviewed Apr 10, 2025

View reviewed changes

Navigation Menu

Repository navigation

fix: Room - No animation when returning to room settings after saving new room description. - #54623

fix: Room - No animation when returning to room settings after saving new room description.#54623
jasperhuangg merged 4 commits into
Expensify:mainfrom
Krishna2323:krishna2323/issue/53153

Krishna2323 commented Dec 27, 2024 •

edited

Loading

Uh oh!

melvin-bot Bot commented Dec 27, 2024

Uh oh!

Pujan92 commented Dec 30, 2024 •

edited

Loading

Uh oh!

Pujan92 Dec 30, 2024

Uh oh!

Krishna2323 Jan 5, 2025

Uh oh!

Pujan92 left a comment

Uh oh!

OSBotify commented Jan 8, 2025

Uh oh!

github-actions Bot commented Jan 10, 2025

Uh oh!

github-actions Bot commented Jan 11, 2025

Uh oh!

github-actions Bot commented Jan 13, 2025

Uh oh!

c3024 Apr 10, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

Krishna2323 commented Dec 27, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Dec 27, 2024

Uh oh!

Pujan92 commented Dec 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Pujan92 Dec 30, 2024

Choose a reason for hiding this comment

Uh oh!

Krishna2323 Jan 5, 2025

Choose a reason for hiding this comment

Uh oh!

Pujan92 left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Jan 8, 2025

Uh oh!

github-actions Bot commented Jan 10, 2025

Uh oh!

github-actions Bot commented Jan 11, 2025

Uh oh!

github-actions Bot commented Jan 13, 2025

Uh oh!

c3024 Apr 10, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Krishna2323 commented Dec 27, 2024 •

edited

Loading

Pujan92 commented Dec 30, 2024 •

edited

Loading