github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #417] [CLOSED] fix: move history to a shared variable #3118

New Issue
Closed
opened 2026-02-28 20:36:42 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:36:42 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/417
Author: @MatissJanis
Created: 12/31/2022
Status: ❌ Closed

Base: master ← Head: matiss/history

📝 Commits (1)

  • 5a160f0 fix: move history to a shared variable

📊 Changes

4 files changed (+22 additions, -29 deletions)

View changed files

📝 packages/desktop-client/src/components/FinancesApp.js (+11 -17)
📝 packages/desktop-client/src/components/manager/ManagementApp.js (+2 -5)
📝 packages/desktop-client/src/global-events.js (+6 -7)
➕ packages/desktop-client/src/history.js (+3 -0)

📄 Description

Currently history variable is instatiated 2x. Once in ManagementApp and once in FinanceApp.

When a customer is setting up the app for the first time and when he is redirected from ManagementApp to FinanceApp - the history context gets recreated. This also means we sometimes lost history.push("/new-page") action.

The fix is rather simple - to use a single, consistent history variable that is instatiated only one time.

🔄 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/417 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 12/31/2022 **Status:** ❌ Closed **Base:** `master` ← **Head:** `matiss/history` --- ### 📝 Commits (1) - [`5a160f0`](https://github.com/actualbudget/actual/commit/5a160f0818b81249a2a77cc82015b3e346537ad6) fix: move history to a shared variable ### 📊 Changes **4 files changed** (+22 additions, -29 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/FinancesApp.js` (+11 -17) 📝 `packages/desktop-client/src/components/manager/ManagementApp.js` (+2 -5) 📝 `packages/desktop-client/src/global-events.js` (+6 -7) ➕ `packages/desktop-client/src/history.js` (+3 -0) </details> ### 📄 Description Currently `history` variable is instatiated 2x. Once in `ManagementApp` and once in `FinanceApp`. When a customer is setting up the app for the first time and when he is redirected from `ManagementApp` to `FinanceApp` - the history context gets recreated. This also means we _sometimes_ lost `history.push("/new-page")` action. The fix is rather simple - to use a single, consistent `history` variable that is instatiated only one time. --- <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-02-28 20:36:42 -06: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
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#3118
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?