github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 04:18:51 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[PR #2281] [MERGED] [Bugfix] Goals: Database entry #30151

New Issue
Closed
opened 2026-04-18 06:35:06 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-18 06:35:06 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/2281
Author: @shall0pass
Created: 1/24/2024
Status: ✅ Merged
Merged: 1/24/2024
Merged by: @shall0pass

Base: master ← Head: goalDatabaseEntry

📝 Commits (3)

📊 Changes

2 files changed (+9 additions, -1 deletions)

View changed files

📝 packages/loot-core/src/server/budget/actions.ts (+3 -1)
➕ upcoming-release-notes/2281.md (+6 -0)

📄 Description

There is an error in the database insertion if the entry doesn't initially exist when applying goal templates.

Previously an entry like this:
image

would be created. With this change, an entry like this:
image

will be created. The issue I was seeing was that the color coded goal templates were not always rendering color, and in the process of tracking the issue down discovered this as the root issue.

🔄 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/2281 **Author:** [@shall0pass](https://github.com/shall0pass) **Created:** 1/24/2024 **Status:** ✅ Merged **Merged:** 1/24/2024 **Merged by:** [@shall0pass](https://github.com/shall0pass) **Base:** `master` ← **Head:** `goalDatabaseEntry` --- ### 📝 Commits (3) - [`d4da55d`](https://github.com/actualbudget/actual/commit/d4da55d79a746f4cc785c977b3eace27bd156d72) fix database insertion - [`d9d9d01`](https://github.com/actualbudget/actual/commit/d9d9d01df7e5b3839f1991c74ad9c21d4179e941) dbMonth format - [`8bc8113`](https://github.com/actualbudget/actual/commit/8bc81135dfdbf2d5d3b07f882127e4c0140b61a5) release note ### 📊 Changes **2 files changed** (+9 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/src/server/budget/actions.ts` (+3 -1) ➕ `upcoming-release-notes/2281.md` (+6 -0) </details> ### 📄 Description There is an error in the database insertion if the entry doesn't initially exist when applying goal templates. Previously an entry like this: ![image](https://github.com/actualbudget/actual/assets/20625555/e53df2c5-b0aa-4941-885c-5df67b88b417) would be created. With this change, an entry like this: ![image](https://github.com/actualbudget/actual/assets/20625555/7d6b2f1c-70ed-49d4-92cc-02bc29c976d1) will be created. The issue I was seeing was that the color coded goal templates were not always rendering color, and in the process of tracking the issue down discovered this as the root issue. --- <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-04-18 06:35:06 -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
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#30151
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?