github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[PR #5790] fix live report time ranges #13176

New Issue
Closed
opened 2026-04-10 21:48:58 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-10 21:48:58 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/5790

State: closed
Merged: Yes

Fixes https://discord.com/channels/937901803608096828/1389677350215618623/1420520966295126036

This was a balance between retaining the existing behaviour and keeping the changes from https://github.com/actualbudget/actual/pull/5753. I settled on this way because I imagine most people will not add transactions in future months, so they wouldn't see a difference. If you do though, the ranges will push on to the month with the furthest ahead transaction in it, which I can only assume is what you wanted if you added transactions to them.

WDYT? We could also just revert the behaviour so the live ranges just push to the current month and ignore the future transactions but IMO that would go against https://github.com/actualbudget/actual/pull/5753.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/5790 **State:** closed **Merged:** Yes --- Fixes https://discord.com/channels/937901803608096828/1389677350215618623/1420520966295126036 This was a balance between retaining the existing behaviour and keeping the changes from https://github.com/actualbudget/actual/pull/5753. I settled on this way because I imagine most people will not add transactions in future months, so they wouldn't see a difference. If you do though, the ranges will push on to the month with the furthest ahead transaction in it, which I can only assume is what you wanted if you added transactions to them. WDYT? We could also just revert the behaviour so the live ranges just push to the current month and ignore the future transactions but IMO that would go against https://github.com/actualbudget/actual/pull/5753.
GiteaMirror added the pull-request label 2026-04-10 21:48:58 -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#13176
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?