-
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-06-06] Hold is incorrectly lowercase in the dot separator pattern #42437
Comments
Triggered auto assignment to @rlinoz ( |
Triggered auto assignment to @bfitzexpensify ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:
Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it. |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Not a blocker, will take a look shortly though. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Hold is incorrectly lowercase in the dot separator pattern What is the root cause of that problem?In money request preview, we have a function In the case of this issue, the App/src/components/ReportActionItem/MoneyRequestPreview/MoneyRequestPreviewContent.tsx Line 156 in a6cb60c
The function In our case, the function We can check that when we change the language to Spanish What changes do you think we should make in order to solve the problem?inside case 'hold':
return translate('iou.hold'); POC: What changes do you think we should make in order to solve the problem?We can also dismiss the case of if (violations?.[0] && violations?.[0].name !== 'hold') { |
Opening a PR today. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.77-11 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-06-06. 🎊 |
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:
|
Adding a BZ buddy for payment - I will be OOO until June 11th |
Triggered auto assignment to @kadiealexander ( |
Wait, actually, this was all internal, so we can just close this out. |
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.74-4
Reproducible in staging?: y
Reproducible in production?: no
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: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1716249633077769
Action Performed:
Expected Result:
The dot separator pattern should say Cash * Hold
Actual Result:
The dot separator pattern should say Cash * hold
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @bfitzexpensifyThe text was updated successfully, but these errors were encountered: