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

Display both names for IOU Report Previews #23043

Merged
merged 19 commits into from
Aug 8, 2023
Merged

Display both names for IOU Report Previews #23043

merged 19 commits into from
Aug 8, 2023

Conversation

Gonals
Copy link
Contributor

@Gonals Gonals commented Jul 17, 2023

cc @shawnborton , I'm using the existing/standard Multiple Avatar here, but you may want to take a look in case we want some tweaks

Details

Fixed Issues

$ #21102
PROPOSAL:

Tests

  1. Log into an account (A)
  2. Open a chat with a second account (B) and request money
  3. Confirm the report preview displays with both avatars and both names:
Screenshot 2023-07-17 at 10 55 15 PM
  1. Log into B and confirms it displays the same for them.
  2. Log back into A and open a Workspace chat. Request money
  3. Confirm both your name and the workspace name display, as well as both avatars
Screenshot 2023-07-17 at 10 55 25 PM
  • 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 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 Screenshot 2023-07-17 at 10 55 35 PM
Mobile Web - Chrome
Mobile Web - Safari Screenshot 2023-07-21 at 11 21 08 AM
Desktop Screenshot 2023-07-21 at 10 29 54 AM
iOS Screenshot 2023-07-21 at 11 40 05 AM
Android Screenshot 2023-07-21 at 11 18 53 AM

@Gonals Gonals requested a review from a team as a code owner July 17, 2023 21:13
@Gonals Gonals self-assigned this Jul 17, 2023
@melvin-bot melvin-bot bot requested review from aimane-chnaif and removed request for a team July 17, 2023 21:13
@melvin-bot
Copy link

melvin-bot bot commented Jul 17, 2023

@aimane-chnaif 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]

@Gonals
Copy link
Contributor Author

Gonals commented Jul 17, 2023

I'll add the screenshots tomorrow

@Gonals
Copy link
Contributor Author

Gonals commented Jul 18, 2023

@aimane-chnaif, ngrok is being a pain today, so I haven't been able to take the screenshots, but this is ready for review, so feel free to go for it!

@JmillsExpensify
Copy link

@aimane-chnaif Up to you whether you want to start before or after the screenshots are added, though I wanted to give you a heads up that this is one of our more valuable PRs at the moment. Thanks!

@aimane-chnaif
Copy link
Contributor

@aimane-chnaif Up to you whether you want to start before or after the screenshots are added, though I wanted to give you a heads up that this is one of our more valuable PRs at the moment. Thanks!

Got it. Will prioritize review today

@aimane-chnaif
Copy link
Contributor

@Gonals there's conflict

@Gonals
Copy link
Contributor Author

Gonals commented Jul 21, 2023

@Gonals there's conflict

Solved!

@Gonals
Copy link
Contributor Author

Gonals commented Jul 21, 2023

Added screenshots. Android web is not launching for me for reasons unknown (not even in main), but I think it is safe to say this works 😁

let secondaryAvatar = {};
const displayAllActors = props.action.actionName === CONST.REPORT.ACTIONS.TYPE.REPORTPREVIEW && props.iouReport;
if (displayAllActors) {
const secondaryUserDetails = props.personalDetailsList[props.iouReport.ownerAccountID] || {};
Copy link
Contributor

Choose a reason for hiding this comment

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

This is not correct. action.actorAccountID and iouReport.ownerAccountID can be same.

@aimane-chnaif
Copy link
Contributor

Some style issues:

Screenshot 2023-07-24 at 4 07 20 PM

@aimane-chnaif
Copy link
Contributor

Same user info as I commented here - #23043 (comment)

Screen.Recording.2023-07-24.at.3.52.47.PM.mov

@Gonals
Copy link
Contributor Author

Gonals commented Jul 25, 2023

Same user info as I commented here - #23043 (comment)

Screen.Recording.2023-07-24.at.3.52.47.PM.mov

That's a nice catch! How did you manage to get this situation? I see it correctly regardless of which account I'm logged into @aimane-chnaif

@aimane-chnaif
Copy link
Contributor

@Gonals did you test with both payer account and payee account?

@Gonals
Copy link
Contributor Author

Gonals commented Jul 25, 2023

@Gonals did you test with both payer account and payee account?

I did, yeah! That's why I'm surprised:

Screenshot 2023-07-25 at 1 45 56 PM Screenshot 2023-07-25 at 1 46 11 PM

@aimane-chnaif
Copy link
Contributor

ok, I will test again with 2 fresh accounts. Meanwhile, please check style issues

@Gonals
Copy link
Contributor Author

Gonals commented Aug 7, 2023

@aimane-chnaif conflicts solved! Let's get this merged before we get more 😆

@Gonals
Copy link
Contributor Author

Gonals commented Aug 7, 2023

@aimane-chnaif quick ping to get this merged!

@aimane-chnaif
Copy link
Contributor

reviewing now

@Gonals
Copy link
Contributor Author

Gonals commented Aug 8, 2023

Travis happy!

@aimane-chnaif
Copy link
Contributor

On mobile, it's almost impossible to see 2nd person name if 1st name is long. We can discuss how to improve this as a follow-up

Screenshot 2023-08-08 at 3 07 25 PM

@Gonals
Copy link
Contributor Author

Gonals commented Aug 8, 2023

On mobile, it's almost impossible to see 2nd person name if 1st name is long. We can discuss how to improve this as a follow-up

Screenshot 2023-08-08 at 3 07 25 PM

Yep, this sounds like a follow-up issue

@aimane-chnaif
Copy link
Contributor

Screenshots/Videos

IOU request

payer:

Screen.Recording.2023-08-08.at.3.09.38.PM.mov

payee:

Screen.Recording.2023-08-08.at.3.09.54.PM.mov

Expense request

payer:

Screen.Recording.2023-08-08.at.3.13.57.PM.mov

payee:

Screen.Recording.2023-08-08.at.3.14.11.PM.mov

@aimane-chnaif
Copy link
Contributor

As discussed, tooltip issue is handled in follow-up PR (for tracking, let's create GH)
And there's possibility that same user is showing for old money requests - #23043 (comment) but as it's not constantly reproducible, let's consider this not regression for now.

@melvin-bot melvin-bot bot requested a review from dangrous August 8, 2023 14:19
@melvin-bot
Copy link

melvin-bot bot commented Aug 8, 2023

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

Copy link
Contributor

@dangrous dangrous left a comment

Choose a reason for hiding this comment

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

LGTM! I see there are a number of follow up issues we'll have to work on (tooltips, etc.) but seems like this is a good base for those to come from

@dangrous dangrous merged commit dab2905 into main Aug 8, 2023
12 checks passed
@dangrous dangrous deleted the alberto-bothNames branch August 8, 2023 14:39
@OSBotify
Copy link
Contributor

OSBotify commented Aug 8, 2023

✋ 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
Copy link
Contributor

OSBotify commented Aug 9, 2023

🚀 Deployed to staging by https://github.com/dangrous in version: 1.3.52-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Aug 9, 2023

🚀 Deployed to staging by https://github.com/dangrous in version: 1.3.52-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.52-5 🚀

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

@jjcoffee
Copy link
Contributor

Just flagging that this PR introduced an issue where we'd end up with a duplicate participant name & avatar if a user who got a money request requests money back. This happened because secondaryUserDetails can end up being the same as the primary (actor) once they request money back.

const secondaryUserDetails = props.personalDetailsList[props.iouReport.ownerAccountID] || {};
const secondaryDisplayName = lodashGet(secondaryUserDetails, 'displayName', '');

More details here.

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.

9 participants