Refactoring recurring transactions #167
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This aims to address #144. I focused on Backend operations only.
Removed recurring_transaction_amount model, and added recurring_transaction.
Now we've a table that list recurring transactions. When the app is opened, not more than once a day thanks to shared preferences, system will check if a transaction (or more) is needed, and adds them to the transaction table, based on their recurrency type.
Also changed the behavior of "clear db" button on settings: now it re-generates all tables. This is useful when we edit models: there will no more need to delete database from OS.
To check this PR, just chekout, run, press "reset DB" and fill with demo data.
I'm leaving this in draft for now: i need to go deeper on some behaviors, update tests, and remove some dev debug code.
Meanwhile feel free to share your opinions if you want.
Also if anyone wants to help with frontend, which I am not very familiar with, it would help.