-
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 2024-08-19] Suggestions causing excessive updates #46810
Comments
Triggered auto assignment to @twisterdotcom ( |
Triggered auto assignment to @neil-marcellini, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@neil-marcellini Since I reviewed the PR, can you please assign me to this issue? TIA 😄 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.18-10 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-08-19. 🎊 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:
|
I think no regression test is needed, this is only something that can come up during development |
Let's close now then, no payment, no regression tests needed. |
I think there will be payment left for me. I reviewed the PR |
Ah, you're right! Sorry for missing that @hungvu193. |
Payment Summary:
|
$250 approved for @hungvu193 |
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:v9.0.16-4 Develop
Reproducible in staging?: No, but there no warning will be thrown, although the performance impact is there
Reproducible in production?: No, but there no warning will be thrown, although the performance impact is there
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):n/a
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:@hannojg
Slack conversation:
Action Performed:
Expected Result:
None of our components rerenders excessively while typing.
Actual Result:
Although there are no visible changes, internally we queue lots of react state updates.
Workaround:
No, its more of a performance issue.
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Screen.Recording.2024-07-19.at.19.11.12.mov
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: