-
-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recurring expenses #5
Comments
Hi @whatisthisidont, yes that would be an interesting feature, just need to think about how it could work. Creation flow:
Deletion flow:
Edition flow:
|
You could mirror it off of like Outlook recurring meetings. If you attempt to update or delete a future meetings, it gives a prompt for all/future/individual essentially. For the initial release, I think defaulting to editing/deleting a recurring expense could apply to all future expenses only. |
Hi |
Hello, wanting this feature as well. :) |
This feature is what's stopping (mostly) me from migrating from split wise. A nice addition to this would be an end date for the recurring expense (optional) |
It looked like the last PR had been inactive for a bit and had several merge conflicts that I was having issues resolving. However, I took some inspiration from its implementation for this PR^. (Note: This was also the last feature I was really waiting for to be able to switch off of SplitWise, so I have some extra motivation to try to get it through) |
@terrencetjr24 thank you so much for that PR. i am basically waiting for this to be merged before switching. i am currently using cospend and am quite happy with it. however i plan to ditch nextcloud in the foreseeable future and then... well then i NEED this. :) |
@scastiel Looking forward to seeing this crucial feature merged |
hi!
really loving and appreciating this project.
i was wondering whether recurring expenses are a feature that you'd consider adding.
with that, transitioning from splitwise would be a no-brainer, for me and i'm assuming for others.
thanks so much
The text was updated successfully, but these errors were encountered: