-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2023-06-21] [$1000] Update user tooltips to include avatar, display name, and handle #20086
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01630563c7656399b7 |
Triggered auto assignment to @mallenexpensify ( |
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Triggered auto assignment to @aldo-expensify ( |
Sorry @trjExpensify @aldo-expensify @mallenexpensify. I'll manage this one. |
ProposalPlease re-state the problem that we are trying to solve in this issue.We have to update user tooltips to include an avatar, display name, and handle address, right now it is only the email address What is the root cause of that problem?This is more like a feature request before we only show the email What changes do you think we should make in order to solve the problem?Here at ReportActionItemSingle Component, we are showing actorEmail on ToolTip App/src/pages/home/report/ReportActionItemSingle.js Lines 103 to 110 in fc30ddc
here, We need to remove the text prop and need to use renderTooltipContent for rendering Avatar, name and address
We have to handle a similar case for the email address beside Avatar In the Message header, At ReportActionItemSingle Component we have ReportActionItemFragment for rendering the email text and here we are passing App/src/pages/home/report/ReportActionItemSingle.js Lines 123 to 130 in fc30ddc
App/src/pages/home/report/ReportActionItemFragment.js Lines 146 to 153 in fc30ddc
Resultupadte-name.movWhat alternative solutions did you explore? (Optional)none |
ProposalPlease re-state the problem that we are trying to solve in this issue.Update user tooltips which shows more details of the user instead of just email/loginid What is the root cause of that problem?Currently, we are only passing a string of the actor emailid/loginid for the user tooltip. What changes do you think we should make in order to solve the problem?For this new feature, we need to create a new general component called Similar kind of behaviour we have for reaction tooltip content here. App/src/components/Reactions/ReportActionItemReactions.js Lines 74 to 76 in fc30ddc
|
@Nikhil-Vats yes! |
@puneetlath Thanks, I will work on one then! |
Hi! - I think this other GH #20052 is the same issue as this one, could you please take a peek and let me know if you agree? |
@Christinadobrzyn I think issues are different, this is a new feature where we will update existing tooltips , however the other issue #20052 , the tooltip itself is missing |
Love the thorough review @fedirjh. @cloudpresser let's do it. |
📣 @cloudpresser You have been assigned to this job by @puneetlath! |
@cloudpresser what's your ETA for when you could have a PR up? |
@puneetlath I will have a PR tomorrow before 12pm EST. |
PR is close to merging. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.27-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-06-21. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Commented on the PR as well, but I think we need to handle workspace avatars case: https://expensify.slack.com/archives/C049HHMV9SM/p1686821040533159 |
@cloudpresser @fedirjh sorry for the delay. Sent you both hiring offers. |
@puneetlath Thanks, accepted. |
@cloudpresser friendly bump on accepting the Upwork offer. That way I can get you paid and we can close out this issue. Thanks! |
@puneetlath Accepted, thanks |
All paid. Thanks for the effort everyone! Looking forward to your future contributions 💪🏾 |
Today our user tooltips look like this:
We want to update them to look like this:
Things to note:
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: