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

Closed
opened 2026-06-05 18:54:26 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/5636
Author: @MatissJanis
Created: 8/26/2025
Status: Closed

Base: masterHead: cursor/analyze-performance-issues-with-large-transaction-sets-fb8d


📝 Commits (1)

  • a45c63c Simplify transaction save logic in TransactionList component

📊 Changes

1 file changed (+1 additions, -7 deletions)

View changed files

📝 packages/desktop-client/src/components/transactions/TransactionList.tsx (+1 -7)

📄 Description

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

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/5636 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 8/26/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `cursor/analyze-performance-issues-with-large-transaction-sets-fb8d` --- ### 📝 Commits (1) - [`a45c63c`](https://github.com/actualbudget/actual/commit/a45c63c6f1215c2dffd9e2946317b5fb90bd97d6) Simplify transaction save logic in TransactionList component ### 📊 Changes **1 file changed** (+1 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/transactions/TransactionList.tsx` (+1 -7) </details> ### 📄 Description <!-- 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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-05 18:54:26 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#112861