mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-13 13:43:35 -05:00
[GH-ISSUE #1039] [Feature] Retain months viewed range #7343
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#7343
Reference in New Issue
Block a user
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?
Originally created by @youngcw on GitHub (May 16, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1039
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
When viewing multiple months in the budget window I like to set the view to last/current/next month. Ex. at time of writing I would look at the budgets for April/May/June.
The next time I open the browser window I still can view 3 months, but it starts at the current month instead of remembering the last used range.
Describe your ideal solution to this problem
Save the viewed months in the cached data along with the number of months viewed so a user can jump back in to the same setup as the last time.
Teaching and learning
No response
@github-actions[bot] commented on GitHub (May 16, 2023):
✨ Thanks for sharing your idea! ✨
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!
@youngcw commented on GitHub (Jul 27, 2023):
Im happy that #1237 got merged in. Would it be doable to retain the viewed range per budget instead of across all budgets? I often jump between main/business/testing budgets and would prefer they each retained their own view range
@j-f1 commented on GitHub (Jul 27, 2023):
I believe they are stored on the local prefs object which should be separate for each budget file.
@youngcw commented on GitHub (Jul 27, 2023):
Im seeing the view retained between different files. I can set it to something crazy like 6 months starting a year ago, then close the file and open another and get that same view
@youngcw commented on GitHub (Jul 27, 2023):
hmm, I was seeing it sometimes, but now it seems to be gone. Maybe the version I was on before updating didn't have that PR yet.
I am still consistently seeing that the number of viewed months doesn't stay within a single file.
@j-f1 commented on GitHub (Jul 27, 2023):
Phew! I checked the code and it looks like the local prefs are always cleared when closing a file, but maybe we missed something since the current open budget state is stored on both the server and client sides in the browser independently.
That is intentional since the
maxMonthspref is stored in the globalPrefs. I don’t really feel strongly that it needs to be there, though.@youngcw commented on GitHub (Jul 27, 2023):
I would be onboard with changing that pref to be per file instead of global.
@youngcw commented on GitHub (Jul 28, 2023):
probably can remove
needs votes. Maybe if the number of months being across all files is annoying enough it can get its own feature request.@j-f1 commented on GitHub (Jul 28, 2023):
Yep! The automation failed 🤦
Hopefully fixing in #1411