We used to use "regularity" (IsRegular) to describe whether a transaction is a regularly appeared item. That is, whether we have to spend this money each month (subscription) or each year (tax, subscription). It aims to predict of the expense in the future. However, we never have the need to implement this prediction. Also, we don't know how "regular" this expense is. So I believe it's not adapted to our analysis. I suggest to remove it to simplify the final output.
If we need this feature again, I suggest we centralize the control in the configuration:
Create a "scheduled" section in the configuration (finance-tools.yml)
Each scheduled item contains an expression to determine whether a transaction belongs to this item.
Each scheduled item contains an optional start date and end date
Each scheduled item contains a scheduled period: day, month, quarter, year
Taking Netflix subscription as an example, it's an item called "netflix" that is scheduled at a monthly basis and contains a start date (2022-01-08) and does not contain an end date (scheduled infinitely). It matches .*NETFLIX.* in the transaction label.
We used to use "regularity" (
IsRegular) to describe whether a transaction is a regularly appeared item. That is, whether we have to spend this money each month (subscription) or each year (tax, subscription). It aims to predict of the expense in the future. However, we never have the need to implement this prediction. Also, we don't know how "regular" this expense is. So I believe it's not adapted to our analysis. I suggest to remove it to simplify the final output.If we need this feature again, I suggest we centralize the control in the configuration:
finance-tools.yml)Taking Netflix subscription as an example, it's an item called "netflix" that is scheduled at a monthly basis and contains a start date (2022-01-08) and does not contain an end date (scheduled infinitely). It matches
.*NETFLIX.*in the transaction label.