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

Move Leave button into a row of the Report Details page #41823

Conversation

ZhenjaHorbach
Copy link
Contributor

Details

Move the "Share" row into the ChatDetailsQuickActionsBar

Move the "Leave" button out of this component and into it's own row here.

Fixed Issues

$ #40256
PROPOSAL: #40256 (comment)

Tests

  1. Open App
  2. Open any GroupChat or Room
  3. Press on header and open details
  4. Verify that Pin and Share buttons are in ActionBar and leave button is in Menu list at the end
  • Verify that no errors appear in the JS console

Offline tests

  1. Open App
  2. Open any GroupChat or Room
  3. Press on header and open details
  4. Verify that Pin and Share buttons are in ActionBar and leave button is in Menu list at the end

QA Steps

  1. Open App
  2. Open any GroupChat or Room
  3. Press on header and open details
  4. Verify that Pin and Share buttons are in ActionBar and leave button is in Menu list at the end
  • 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 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 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 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.

Screenshots/Videos

Android: Native
android_w5JoDfzq.mp4
Android: mWeb Chrome
android_w5JoDfzq.mp4
iOS: Native
ios_C82AYGGZ.mp4
iOS: mWeb Safari
ios-web_D4Z5n1mS.mp4
MacOS: Chrome / Safari
web_YDYEn9BO.mp4
MacOS: Desktop
desktop_7RFrq62O.mp4

@ZhenjaHorbach ZhenjaHorbach requested a review from a team as a code owner May 8, 2024 07:24
@melvin-bot melvin-bot bot requested review from DylanDylann and removed request for a team May 8, 2024 07:24
Copy link

melvin-bot bot commented May 8, 2024

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

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented May 8, 2024

@DylanDylann
Hello
PR is ready
I'm using !isGroupDMChat for showing ChatDetailsQuickActionsBar to fix regressions related with Share button display

https://github.com/Expensify/App/pull/41823/files#diff-409b0e2fb439856e9897b808014031ce244a427d116ed30f37a2e0117599adc4R364

This condition we used before

https://github.com/Expensify/App/pull/41823/files#diff-409b0e2fb439856e9897b808014031ce244a427d116ed30f37a2e0117599adc4L123-L132

The only thing
I'm a little unsure whether we should show a Pin button with the same condition?
What do you think ?

@DylanDylann
Copy link
Contributor

@ZhenjaHorbach ref: #40256 (comment)

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented May 9, 2024

@ZhenjaHorbach ref: #40256 (comment)

In the current changes I use the condition for ChatDetailsQuickActionsBar that we use for Share button at the moment

@DylanDylann
Copy link
Contributor

DylanDylann commented May 13, 2024

@ZhenjaHorbach We will apply ChatDetailsQuickActionsBar for all reports but we will not display pin/unpin option in all reports. Let's keep the options as before. This is discussed here

@DylanDylann
Copy link
Contributor

For example in admin room, we only display Share button

Screenshot 2024-05-13 at 17 40 28

When migrating to use ChatDetailsQuickActionsBar we also need to ensure that ChatDetailsQuickActionsBar only has Share button

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented May 13, 2024

@ZhenjaHorbach We will apply ChatDetailsQuickActionsBar for all reports but we will not display pin/unpin option in all reports. Let's keep options as before

I was just writing a comment about this )
I can't think of a case why we shouldn't display pin buttons everywhere
Because just look at the header report, where the pin button is always present

In fact, it's a little confusing this discrepancy between the header and details page

And during this comment we want use pin everywhere where we can do it
#40256 (comment)

@ZhenjaHorbach
Copy link
Contributor Author

@DylanDylann
https://github.com/Expensify/App/pull/41823/files#diff-409b0e2fb439856e9897b808014031ce244a427d116ed30f37a2e0117599adc4L123-L131

@ZhenjaHorbach We will apply ChatDetailsQuickActionsBar for all reports but we will not display pin/unpin option in all reports. Let's keep the options as before. This is discussed here

@DylanDylann

And if I understand you correctly, you mean to show the pin button only for isGroupChat || isChatRoom ?
Like here
https://github.com/Expensify/App/pull/40979/files#diff-409b0e2fb439856e9897b808014031ce244a427d116ed30f37a2e0117599adc4R363

@DylanDylann
Copy link
Contributor

@ZhenjaHorbach Let's wait for the final decision from the design team before moving forward with the PR. Thanks

@ZhenjaHorbach
Copy link
Contributor Author

@ZhenjaHorbach Let's wait for the final decision from the design team before moving forward with the PR. Thanks

I just fixed the conflicts)
But agree, let's wait for the final decision

@@ -332,7 +354,7 @@ function ReportDetailsPage({policies, report, session, personalDetails}: ReportD
/>
</OfflineWithFeedback>
)}
{isGroupChat && <ChatDetailsQuickActionsBar report={report} />}
<ChatDetailsQuickActionsBar report={report} />
Copy link
Contributor

Choose a reason for hiding this comment

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

@ZhenjaHorbach From my viewpoint, we should update like this

Suggested change
<ChatDetailsQuickActionsBar report={report} />
{!isGroupDMChat && <ChatDetailsQuickActionsBar report={report} />}

To make sure the logic to display the share button is same like before

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will update this line
If something happens, I'll revert the last commit
If we decide to use it everywhere

const isPrivateNotesFetchTriggered = report?.isLoadingPrivateNotes !== undefined;

const isSelfDM = useMemo(() => ReportUtils.isSelfDM(report), [report]);

const shouldShowReportDescription = isChatRoom && (canEditReportDescription || report.description !== '');
Copy link
Contributor

Choose a reason for hiding this comment

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

Revert the position of this variable to keep the change is clean

translationKey: 'common.leave',
icon: Expensicons.Exit,
isAnonymousAction: true,
shouldShowRightIcon: false,
Copy link
Contributor

Choose a reason for hiding this comment

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

Should add shouldShowRightIcon: true to other item

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry
I probably didn't fully understand you
But we only have one place where we don't need an icon
For other cases I have added a condition here

https://github.com/Expensify/App/pull/41823/files#diff-409b0e2fb439856e9897b808014031ce244a427d116ed30f37a2e0117599adc4R369

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah, the current change work well, but I think add shouldShowRightIcon: true to other item will be clearer

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahhhh
I understand )
No problem
I'll update now

@DylanDylann
Copy link
Contributor

@ZhenjaHorbach Minor comment and please merge main again. Thanks

@@ -196,10 +196,27 @@ function ReportDetailsPage({policies, report, session, personalDetails}: ReportD
});
}

if ((isGroupChat || (isChatRoom && ReportUtils.canLeaveChat(report, policy ?? null))) && !isThread) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Agree with you at this point && !isThread if it is thread we should display leave row

Copy link
Contributor

Choose a reason for hiding this comment

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

Agree, but sort of out of scope for the original ticket maybe. I believe there is a separate project to make this change.

@DylanDylann
Copy link
Contributor

@ZhenjaHorbach please check TS error

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented May 16, 2024

@ZhenjaHorbach please check TS error

This is normal )
This is a problem in main

I will update the branch when a fix will be in main

@ZhenjaHorbach
Copy link
Contributor Author

@DylanDylann
no more TS errors )

@@ -332,7 +357,7 @@ function ReportDetailsPage({policies, report, session, personalDetails}: ReportD
/>
</OfflineWithFeedback>
)}
{isGroupChat && <ChatDetailsQuickActionsBar report={report} />}
{!isGroupDMChat && <ChatDetailsQuickActionsBar report={report} />}
Copy link
Contributor

Choose a reason for hiding this comment

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

We can pin a Group DM chat, but not share it. They are getting deprecated soon. But, I think this is more or less incorrect logic and we should be able to remove the !isGroupDMChat.

@@ -196,10 +196,27 @@ function ReportDetailsPage({policies, report, session, personalDetails}: ReportD
});
}

if ((isGroupChat || (isChatRoom && ReportUtils.canLeaveChat(report, policy ?? null))) && !isThread) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Agree, but sort of out of scope for the original ticket maybe. I believe there is a separate project to make this change.

@marcaaron
Copy link
Contributor

@ZhenjaHorbach found one thing if you can fix it - otherwise, looks great.

Thanks for your patience both @DylanDylann and @ZhenjaHorbach as we had temporarily halted merging of PRs, but now resumed. 🙇

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented May 28, 2024

Fix comments

@marcaaron

I updated the branch and fixed comments
f6202cc

style={styles.flex1}
text={isPinned ? translate('common.unPin') : translate('common.pin')}
text={translate('common.share')}
Copy link
Contributor

Choose a reason for hiding this comment

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

well, we need to add back the if (!isGroupDMChat) to this part now... I thought that was clear from my last comment sorry if not.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, sorry
Perhaps I misunderstood
But I fixed it
And I updated the styles for one button inside ActionsBar following this comment

#40256 (comment)

Copy link
Contributor

Choose a reason for hiding this comment

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

Would you mind posting a screen shot of this change? I want to make sure it's what @shawnborton expects. Thanks!

Copy link
Contributor Author

@ZhenjaHorbach ZhenjaHorbach May 29, 2024

Choose a reason for hiding this comment

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

Something like this if we have one button
Снимок экрана 2024-05-29 в 02 56 59

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we're working on a component for this that has all of that baked in. @grgia does that sound right?

Copy link
Contributor

Choose a reason for hiding this comment

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

Check this PR here: #41972

Just want to make sure we aren't duplicating work.

Copy link
Contributor

Choose a reason for hiding this comment

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

@shawnborton thanks for noticing! It looks like this PR will conflict with #41972

cc @grgia

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the heads up @shawnborton

I think we're good here though. We just need to fix some conflicts now @ZhenjaHorbach. I've instructed @cdOut to pause the next PR they mentioned since we don't really need it.

@grgia might want to do a quick scan to make sure there aren't any other improvements with open issues that snuck into that design doc, but don't think there are a ton. They should all be in the #vip-split project and categorized by Group Chats.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I updated the PR and made changes to use the new implementation for ActionBar

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Although we have TS issue in main
#42798

@marcaaron marcaaron mentioned this pull request May 29, 2024
50 tasks
@melvin-bot melvin-bot bot requested a review from marcaaron May 30, 2024 08:04
Copy link
Contributor

@marcaaron marcaaron left a comment

Choose a reason for hiding this comment

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

Just had one more small request. Rest of the code looks good, but don't think we need isHidden

@@ -19,6 +19,9 @@ type ThreeDotsMenuItem = {

/** A callback triggered when the item is selected */
onSelected: () => void;

/** Whether the item is hidden */
isHidden?: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we have an isHidden prop vs. just not including it in the items passed to the component?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually good idea
Thanks for the review
Done )

{promotedActions.map(({key, onSelected, ...props}) => {
if (props.isHidden) {
return null;
}
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 just exclude it if it should be hidden? Then this can be removed.

@@ -15,7 +18,19 @@ function getPinMenuItem(report: OnyxReport): ThreeDotsMenuItem {
};
}

function getShareMenuItem(report: OnyxReport, participants: number[]): ThreeDotsMenuItem {
const isGroupDMChat = ReportUtils.isDM(report) && participants.length > 1;
Copy link
Contributor

Choose a reason for hiding this comment

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

Check for isGroupDMChat when we are deciding whether to add the share menu item or not. Then delete this method as it is only used in one place.

shouldShowLeaveButton
/>
)}
<PromotedActionsBar promotedActions={[PromotedActions.pin(report), ...(isGroupDMChat ? [] : [PromotedActions.share(report)])]} />
Copy link
Contributor

Choose a reason for hiding this comment

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

NAB but I think it is slightly over engineered to have "pin" and "share" functions that return an object. No need for all these different methods IMO. Just use the objects.

@OSBotify
Copy link
Contributor

OSBotify commented Jun 6, 2024

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.79-11 🚀

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

key: CONST.REPORT_DETAILS_MENU_ITEM.LEAVE_ROOM,
translationKey: 'common.leave',
icon: Expensicons.Exit,
isAnonymousAction: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

Coming from #43404:
@ZhenjaHorbach was there any reason for setting this value to true?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmmm
Actually good question
But I don't think it should be true

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for confirmation

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.

7 participants