github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[PR #5636] Analyze performance issues with large transaction sets #13099

New Issue
Closed
opened 2026-04-10 21:47:13 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-10 21:47:13 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/5636

State: closed
Merged: No

This PR eliminates the "double update" flicker when rapidly editing transactions.

Previously, non-date edits would optimistically update the UI immediately, then trigger a LiveQuery refetch, causing the UI to briefly revert and then re-apply changes. This change removes the optimistic update path for non-date edits, ensuring the UI updates only once via the LiveQuery system after the save, preventing the visual flicker.

Open in Cursor Open in Web
**Original Pull Request:** https://github.com/actualbudget/actual/pull/5636 **State:** closed **Merged:** No --- <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> This PR eliminates the "double update" flicker when rapidly editing transactions. Previously, non-date edits would optimistically update the UI immediately, then trigger a LiveQuery refetch, causing the UI to briefly revert and then re-apply changes. This change removes the optimistic update path for non-date edits, ensuring the UI updates only once via the LiveQuery system after the save, preventing the visual flicker. --- <a href="https://cursor.com/background-agent?bcId=bc-41d4fa3c-ef4d-4318-bfc4-03557934114d"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-cursor-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-cursor-light.svg"> <img alt="Open in Cursor" src="https://cursor.com/open-in-cursor.svg"> </picture> </a> <a href="https://cursor.com/agents?id=bc-41d4fa3c-ef4d-4318-bfc4-03557934114d"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-web-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-web-light.svg"> <img alt="Open in Web" src="https://cursor.com/open-in-web.svg"> </picture> </a>
GiteaMirror added the pull-request label 2026-04-10 21:47:13 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#13099
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?