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-05-26] [No QA] perf: replace lodash mapKeys with native loop in usePersonalDetailsByEmail #90946
The usePersonalDetailsByEmail hook uses lodash/mapKeys to build a map of personal details keyed by login. Lodash's mapKeys carries internal type-checking and iteration overhead that is unnecessary for this straightforward transformation, and it introduces an additional lodash dependency into the hook.
Solution
Replace the lodash/mapKeys call with a native for...of loop over Object.entries. This removes the lodash dependency and avoids its internal overhead, producing the same result — a map keyed by each personal detail's login (falling back to the original key if login is absent). A similar replacement was done in WorkflowUtils in PR #89477 and showed around a 4x performance improvement.
changed the title [-][No QA] perf: replace lodash mapKeys with native loop in usePersonalDetailsByEmail[/-][+][Due for payment 2026-05-26] [No QA] perf: replace lodash mapKeys with native loop in usePersonalDetailsByEmail[/+]on May 19, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.77-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon May 19, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".[-][No QA] perf: replace lodash mapKeys with native loop in usePersonalDetailsByEmail[/-][+][Due for payment 2026-05-26] [No QA] perf: replace lodash mapKeys with native loop in usePersonalDetailsByEmail[/+]melvin-bot commentedon May 19, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.77-3 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-05-26. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 20, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon May 25, 2026
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon May 26, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon May 27, 2026
Payment Summary
Contributor+: @abzokhattab due $125 via NewDot
No tests needed, perf
quinthar commentedon Jun 29, 2026
Approved $125 to @abzokhattab