You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-08-19] [$250] Remove unnecessary types from translations #76429
📣 @mrejdak! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Hi @iwiznia, I'll start by replacing all types containing a single parameter. (like the type AddressLineParams below)
typeAddressLineParams={lineNumber: number;}
# addressLine: ({lineNumber}: AddressLineParams)=>`Address line ${lineNumber}`,
# replacedwith:
addressLine: (lineNumber : number)=>`Address line ${lineNumber}`,
Regarding the types defining objects that contain multiple params - should those be replace with standalone parameters as well? (e.g. the CharacterLengthLimitParams type)
Here's the full set of PRs linked to this issue with a suggested payout for each. Total suggested: $2,325 across 15 merged PRs (4 more got $0 — 2 reverted, 2 closed-unmerged).
A quick note on method: these are all mechanical "remove translation types" batches, so I treated the standard repeat batches as low effort ($125), kept the first-of-pattern / unusually-large / real-logic ones at base ($250), and applied the revert/reapply exceptions. Effort tiers are a judgment call — adjust as you see fit.
Follow-up reapply → 50% less:#77501 reapplied batch 1 and #79190 reapplied batch 6. Both carried a real logic fix (skipCache; promptKeyParams/importFinalModal), so I based them at $250 and halved to $125.
Closed, never merged → $0:#76977 and #84400 were superseded duplicates that never landed. Not "reverts" — just no work merged — so no payout.
changed the title [-][$250] Remove unnecessary types from translations[/-][+][Due for payment 2026-08-12] [$250] Remove unnecessary types from translations[/+]on Aug 12, 2026
changed the title [-][Due for payment 2026-08-12] [$250] Remove unnecessary types from translations[/-][+][Due for payment 2026-08-19] [$250] Remove unnecessary types from translations[/+]on Aug 12, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.52-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 2026-08-19. 🎊
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]. If no checklist is needed for this issue, you can click: [no checklist button]
@QichenZhu, originally the issue was $250 and it significantly crew. It's generally best practice to not cram a bunch of PRs together, in this instance there were 15 PRs but the amount of work, overall, didn't justify $2,325. We ended up doing 15 x $75 to get an amount we felt was fair.
Activity
melvin-bot commentedon Dec 1, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @QichenZhu (
External)melvin-bot commentedon Dec 1, 2025
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.zainAwan9175 commentedon Dec 1, 2025
Would like to work on this.
blazejkustra commentedon Dec 1, 2025
As discussed here, @mrejdak is going to work on this, sorry!
iwiznia commentedon Dec 1, 2025
@mrejdak can't assign you till you comment
mrejdak commentedon Dec 2, 2025
Hey! I'm Michał Rejdak from Software Mansion, an expert agency, and I'm commenting for assignment!
melvin-bot commentedon Dec 2, 2025
📣 @mrejdak! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
mrejdak commentedon Dec 2, 2025
Hi @iwiznia, I'll start by replacing all types containing a single parameter. (like the type AddressLineParams below)
Regarding the types defining objects that contain multiple params - should those be replace with standalone parameters as well? (e.g. the CharacterLengthLimitParams type)
220 remaining items
MelvinBot commentedon Aug 12, 2026
Here's the full set of PRs linked to this issue with a suggested payout for each. Total suggested: $2,325 across 15 merged PRs (4 more got $0 — 2 reverted, 2 closed-unmerged).
A quick note on method: these are all mechanical "remove translation types" batches, so I treated the standard repeat batches as low effort ($125), kept the first-of-pattern / unusually-large / real-logic ones at base ($250), and applied the revert/reapply exceptions. Effort tiers are a judgment call — adjust as you see fit.
How the exceptions were applied
Payable subtotal: 10 × $125 ($1,250) + 4 × $250 ($1,000) + 1 × $75 ($75) = $2,325.
[-][$250] Remove unnecessary types from translations[/-][+][Due for payment 2026-08-12] [$250] Remove unnecessary types from translations[/+]melvin-bot commentedon Aug 12, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)joekaufmanexpensify commentedon Aug 12, 2026
Nice, thanks for doing that. We are aligning on this internally here.
[-][Due for payment 2026-08-12] [$250] Remove unnecessary types from translations[/-][+][Due for payment 2026-08-19] [$250] Remove unnecessary types from translations[/+]melvin-bot commentedon Aug 12, 2026
@QichenZhu @mallenexpensify
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.52-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 2026-08-19. 🎊
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]. If no checklist is needed for this issue, you can click: [no checklist button]
mallenexpensify commentedon Aug 13, 2026
Payment Summary
Contributor+: @QichenZhu due $1200 via NewDot
@QichenZhu, originally the issue was $250 and it significantly crew. It's generally best practice to not cram a bunch of PRs together, in this instance there were 15 PRs but the amount of work, overall, didn't justify $2,325. We ended up doing 15 x $75 to get an amount we felt was fair.
QichenZhu commentedon Aug 14, 2026
@mallenexpensify @iwiznia @joekaufmanexpensify I'm fine with whatever you think is fair, but I want to clarify the context around the 15 PRs:
It was decided to split this work into smaller PRs from the start.
I kept the team updated after the 5th and 10th PRs, including the estimated total number of PRs.
So I don't think we deviated from the requested approach. If there were concerns, it would have been better to know earlier so we could adjust course.
trjExpensify commentedon Sep 1, 2026
approved $1,200 for @QichenZhu