-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2022-10-03] [$250] Ellipsis is not showing up in medium screen width - reported by @Tushu17 #10510
Comments
Triggered auto assignment to @bfitzexpensify ( |
Triggered auto assignment to @robertjchen ( |
@robertjchen Eep! 4 days overdue now. Issues have feelings too... |
Should we reassign this one, given you'll be on Sabbatical soon? |
Thanks for the report- I was able to reproduce this issue locally. Going to open this up for our contributors to tackle 👍 |
Triggered auto assignment to @MitchExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @ctkochan22 ( |
ProposalProblemThe issue is from the SolutionThere're 2 solutions that I propose, it's dependent on whether we still want to keep the 'truncated last message text' optimization or not: 1. We keep the last message text length as is without truncating it, when we save it to Onyx (and subsequently to our database) In function formatReportLastMessageText(lastMessageText) {
- return String(lastMessageText).substring(0, CONST.REPORT.LAST_MESSAGE_TEXT_MAX_LENGTH);
+ return String(lastMessageText);
} or we can remove the 2. We increase the We should only consider this if we really want to keep the max last message size (for optimization or some other reasons). In -LAST_MESSAGE_TEXT_MAX_LENGTH: 80,
+LAST_MESSAGE_TEXT_MAX_LENGTH: 200, Issue fixed when implementing each of the above and set the network to offline (because back-end fix is also required so I turn off network to test first) Please let me know if you have any concerns regarding the above proposal |
okayy, I can get onboard with that |
@rushatgabhane I appreciate your thoroughness in thinking through the proposal |
Lets go with solution 2. @christianwen Can you write up the PR and test on all platforms please? |
@ctkochan22 I'm preparing the PR, I've also applied for the Upwork job, please help accept my proposal on Upwork. My Upwork profile is https://www.upwork.com/freelancers/~01991fd5e5c11ef3ba |
@ctkochan22, @rushatgabhane, @MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@MitchExpensify can we hire @christianwen pretty please |
Sorry for the delay, catching up from OOO last week! Hired @christianwen, @Tushu17, and invite sent to @rushatgabhane for eventual C+ payment |
thanks @MitchExpensify |
PR seems okay, we should wait for backend changes before merging? |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.6-0 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 2022-10-03. 🎊 |
@laurenreidexpensify i believe we can settle this issue? |
Issuing payment now! |
Just waiting on you to accept @rushatgabhane before closing this out, thanks everyone! |
Done! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
It should show ellipsis for long message.
Actual Result:
It doesn't show ellipsis.
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.88-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2022-08-03.at.6.38.07.PM.mov
Expensify/Expensify Issue URL:
Issue reported by: @Tushu17
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1659542182865039
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: