-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-05-22] [Due for payment 2025-05-13] [$250] Reducing Search API Calls in Reports Screen #61053
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
Comments
Job added to Upwork: https://www.upwork.com/jobs/~021917145585218173680 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
Current assignee @mountiny is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new. |
Triggered auto assignment to @Christinadobrzyn ( |
Solution is already defined in OP, I would like to work on this task if this will be done by external. |
Thanks! Callstack will handle this |
@martasudol lets please handle this one in one more PR #60896 (comment) |
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. |
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. |
PR reverted. New PR to be opened. |
Payment Summary
BugZero Checklist (@Christinadobrzyn)
|
@Christinadobrzyn , yes, that's correct! |
watching PR - #61499 |
watching PR - #61499 Gonna move this back to weekly since the PR will still need to go through the 7 day window |
Had to be reverted due to blocker unfortunately |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.45-21 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 2025-05-22. 🎊 For reference, here are some details about the assignees on this issue:
|
Triggered auto assignment to @JmillsExpensify ( |
Just a heads up that I'm going to be ooo May 21st - May 27th. Back on the 28th. I'll assign someone to pay this. @c3024 do we need a regression test for this? |
The PR was reverted, so payment is not yet due. |
New PR created here. |
Coming from this proposal.
Background:
When users open an expense report from the "Reports" tab, the application displays the detailed report information. Currently, the useSearchHighlightAndScroll hook is doing more than what its name suggests - beyond just handling UI highlighting and scrolling functions, it's also making API calls to the /Search endpoint. Hooks should ideally have single responsibilities that match their names, but this hook is currently performing data fetching operations that lie outside its intended purpose.
Problem:
When a user opens an expense report, multiple redundant calls to the /Search endpoint are triggered (by useSearchHighlightAndScroll hook), wasting network resources and impacting application performance.
Solution:
We will separate the concerns by:
This separation will maintain functionality while reducing network overhead and improving performance.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @JmillsExpensifyThe text was updated successfully, but these errors were encountered: