github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-08 12:59:01 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #5512] [Feature] Trim leading/trailing whitespace from imported CSV text fields #51493

New Issue
Closed
opened 2026-04-30 18:04:57 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-30 18:04:57 -05:00
Owner
Copy Link

Originally created by @ashanzzz on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5512

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Problem

When importing CSV files (especially those from bank exports or spreadsheets), Actual does not trim leading or trailing whitespace in text fields like "Notes" or "Payee". This can create inconsistent or duplicated entries and waste database space.

Proposed Solution

Offer an optional checkbox in the CSV import UI:
"Trim whitespace from all text fields"
When enabled, all non-numeric text values (Payee, Notes, Category, etc.) should have string.trim() applied before saving.

This will help ensure:

  • Cleaner, consistent data
  • Reduced storage consumption
  • Less manual cleanup in rules and payee lists

Additional Context

It's common for CSV exports to have accidental spaces. Many users manually trim whitespace in external tools, but having built-in support would be far more user-friendly.

Please consider adding this option as a toggle during CSV import. It would significantly enhance data hygiene and user experience.

Thank you!

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @ashanzzz on GitHub (Aug 7, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5512 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? ### Problem When importing CSV files (especially those from bank exports or spreadsheets), Actual does not trim leading or trailing whitespace in text fields like "Notes" or "Payee". This can create inconsistent or duplicated entries and waste database space. ### Proposed Solution Offer an optional checkbox in the CSV import UI: **"Trim whitespace from all text fields"** When enabled, all non-numeric text values (Payee, Notes, Category, etc.) should have `string.trim()` applied before saving. This will help ensure: - Cleaner, consistent data - Reduced storage consumption - Less manual cleanup in rules and payee lists ### Additional Context It's common for CSV exports to have accidental spaces. Many users manually trim whitespace in external tools, but having built-in support would be far more user-friendly. --- Please consider adding this option as a toggle during CSV import. It would significantly enhance data hygiene and user experience. Thank you! ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-30 18:04:58 -05:00
GiteaMirror commented 2026-04-30 18:05:11 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 7, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:3162848268 --> @github-actions[bot] commented on GitHub (Aug 7, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
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 feature needs votes
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#51493
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?