-
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 2023-12-07] [$500] Request money get $250 not formatted correctly #31554
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01f6c623a72781c0f8 |
Triggered auto assignment to @mallenexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Proposal from @allroundexperts ProposalPlease re-state the problem that we are trying to solve in this issue.Request money, get $250 not formatted correctly. What is the root cause of that problem?We have added an extra space here What changes do you think we should make in order to solve the problem?Just remove the extra space here. What alternative solutions did you explore? (Optional)None |
ProposalPlease re-state the problem that we are trying to solve in this issue.Request money, get $250 not formatted correctly. Root causeWe have extra space here: Line 1923 in aeced9a
ChangesWe need to remove the space Line 1923 in aeced9a
|
This should be handled as follow-up of #30372 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Request money, get $250 is not formatted correctly. What is the root cause of that problem?There is an extra space before an amount. What changes do you think we should make in order to solve the problem?Remove that extra space before an amount. What alternative solutions did you explore? (Optional)None |
ProposalPlease re-state the problem that we are trying to solve in this issue.Request money get $250 not formatted correctly What is the root cause of that problem?We have an extra space here, Line 1923 in 475d239
What changes do you think we should make in order to solve the problem?We need to remove this extra space,
What alternative solutions did you explore? (Optional)NA Result: |
@fedirjh , please review the above, reckon it'll be a pretty quick fix. Let me know if you'd like me to loop in a designer to confirm anything. Thx |
@mallenexpensify BTW It's an easy simple fix, I would agree with @situchan #31554 (comment) as the offending PR is still in the regression period. In case we want to fix it separately, then @allroundexperts proposal looks good. |
@mallenexpensify, @fedirjh Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
cc @mallenexpensify friendly bump for #31554 (comment). |
I think this is fixed somehow. |
Hmm, I still see the code was not yet updated : Line 1953 in 4efa2c0
|
Oh, I guess I was mistaken then! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@waterim can I assign this to you since it came from your PR? |
@puneetlath sure, can update this typo |
Thanks! |
📣 @fedirjh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @allroundexperts Please request via NewDot manual requests for the Reporter role ($50) |
Triggered auto assignment to @amyevans, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.5-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-12-07. 🎊 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.
For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@fedirjh can you please accept the job and reply here once you have? |
@amyevans, @mallenexpensify, @fedirjh, @waterim Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mallenexpensify Accepted. Thank you! |
Contributor+: @fedirjh paid $500 via Upwork. I don't think we need to add this to the design/edge case tests we occasionally run, checking with QA to see if anyone disagrees. |
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: 1.4.0-3
Reproducible in staging?: y
Reproducible in production?: seems new feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @allroundexperts
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1700345578210519
Action Performed:
+
fabRequest money, get $250
bottom alert.Expected Result:
Request money, get $250
text to be formatted correctly.Actual Result:
Incorrect formatting (includes an extra space before the amount)
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Recording.246.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: