-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2024-12-17] [$125] Android - Room - Room name displayed truncated on header and details when using long name #52836
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Room title line is broken on room details page. What is the root cause of that problem?App/src/pages/ReportDetailsPage.tsx Line 740 in b7fdace
The line for room title is broken here. What changes do you think we should make in order to solve the problem?We can use What alternative solutions did you explore? (Optional)N/A |
It is expected that we truncate in the header, but we are supposed to show the full name in room details. |
Job added to Upwork: https://www.upwork.com/jobs/~021859338322732202800 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
This is a pretty minor bug, so demoting |
Upwork job price has been updated to $125 |
@Shahidullah-Muffakir Your proposal will be dismissed because you did not follow the proposal template. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Room name is truncated in Room Details page. What is the root cause of that problem?Improvement What changes do you think we should make in order to solve the problem?App/src/pages/ReportDetailsPage.tsx Line 737 in 0c99ad0
here pass a new prop for What alternative solutions did you explore? (Optional) |
Edited by proposal-police: This proposal was edited at 2024-11-21 11:29:27 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Room name displayed truncated on header and details when using long name What is the root cause of that problem?In App/src/pages/ReportDetailsPage.tsx Lines 737 to 738 in 0c99ad0
App/src/components/MenuItem.tsx Line 362 in 0c99ad0
What changes do you think we should make in order to solve the problem?If we do not want to truncate the room name at all we should pass We would also need to update the App/src/components/MenuItem.tsx Line 461 in 00a81dc
const combinedTitleTextStyle = StyleUtils.combineStyles(
[
.........
styles.breakWord,
],
titleStyle ?? {},
);
We did the same thing in previous PR's as well: What alternative solutions did you explore? (Optional) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Let's go with @twilight2294's proposal. We don't want any truncation so it makes sense to make the The first proposal has the correct RCA, but adds a limit on the 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @chiragsalian, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@jjcoffee I don't think passing |
@Shahidullah-Muffakir I have tested it. You can also check out the docs to see that |
@jjcoffee , maybe I am missing something because when I pass |
Screen.20Recording.202024-11-21.20at.203.mp4 |
Room name has a character limit of 100. Considering this, setting
|
PR ready for review @jjcoffee |
PR in review |
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 9.0.68-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 2024-12-07. 🎊 For reference, here are some details about the assignees on this issue:
|
@jjcoffee @joekaufmanexpensify @jjcoffee The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
I see we reverted this PR and are working on a fix in #53308 . I am thinking we'll handle payment once the final PR is out. Sound good @twilight2294 @jjcoffee ? |
Removed payment date, as new PR is not out to prod yet. |
This is pending #53553 , which is merged but not yet out on staging. |
Second PR deployed last week. We'll handle payment here and it is due tomorrow. |
We originally worked on this bug in #53041 and then reverted it because it caused a regression. We then fixed the bug again in #53553. 50% regression penalty therefore applies. Payment here is as follows:
|
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.64-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Room name should be displayed in full in header and on details page, despite using a name with more than 50 characters
Actual Result:
Room name in header and in details is truncated when creating a long room name. (More than 50 characters)
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6653366_1730580575095.Truncated.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @joekaufmanexpensifyThe text was updated successfully, but these errors were encountered: