github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 20:23:07 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #1044] [CLOSED] Allow MEMO to be nested in NAME in OFX parser #3484

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

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/1044
Author: @sinistersnare
Created: 5/18/2023
Status: ❌ Closed

Base: master ← Head: bugfix/ofx-nested-memo

📝 Commits (1)

  • af9d655 Allow MEMO to be nested in NAME in OFX parser

📊 Changes

3 files changed (+38 additions, -9 deletions)

View changed files

📝 packages/desktop-client/src/components/modals/ImportTransactions.js (+1 -1)
📝 packages/loot-core/src/server/accounts/parse-file.ts (+31 -8)
➕ upcoming-release-notes/1044.md (+6 -0)

📄 Description

This comes as a result of some discussion on Discord.

Here is a test-case: https://gist.github.com/sinistersnare/a0b9604f0db25a58cd3f739d427f7f16. Lines 86-89 are the offenders. Should I add this as a unit-test?

🔄 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/1044 **Author:** [@sinistersnare](https://github.com/sinistersnare) **Created:** 5/18/2023 **Status:** ❌ Closed **Base:** `master` ← **Head:** `bugfix/ofx-nested-memo` --- ### 📝 Commits (1) - [`af9d655`](https://github.com/actualbudget/actual/commit/af9d655991732400a3c1824e1009cfef5367d369) Allow MEMO to be nested in NAME in OFX parser ### 📊 Changes **3 files changed** (+38 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/modals/ImportTransactions.js` (+1 -1) 📝 `packages/loot-core/src/server/accounts/parse-file.ts` (+31 -8) ➕ `upcoming-release-notes/1044.md` (+6 -0) </details> ### 📄 Description This comes as a result of some discussion on Discord. Here is a test-case: https://gist.github.com/sinistersnare/a0b9604f0db25a58cd3f739d427f7f16. Lines 86-89 are the offenders. Should I add this as a unit-test? --- <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:42:19 -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#3484
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?