|
|
3521d4c126
|
make radio button for min / avg / max growth value be pushed into which_growth in the DB for bill_type row, then also delete estimated bills for that bill_type, and then calling /bills, causes the estimated bills to be filled back in based on the new chosen growth model
|
2025-08-21 18:20:32 +10:00 |
|
|
|
cd7eca0c6e
|
simplified when we calc totals and hence growth, applied monthly growth annually
|
2025-08-21 16:52:37 +10:00 |
|
|
|
d7320e8aa8
|
remove num we now use - bill_info[bill_type][num_ann_bills], fix bug where we were re-adding first year bills
|
2025-08-20 18:21:52 +10:00 |
|
|
|
5556b0ef15
|
removed debugs, actually add new bills when needed for monthly and annual, support new growth fields, ensure growth only works on real bills not new estimated bills.
|
2025-08-20 18:11:00 +10:00 |
|
|
|
7ac7acf44c
|
major rewrite, took on-board thoughts in TODO, have completely re-written how we process bill_data, and then subsequent growth. Much simpler now (although still complex) - most is now done in one loop to take DB data nd reformat it into an in memory data structure, then process that a few different ways to see missing and future bills, and then calc growths. Still much to go, I do calc missing/future annual bills, but I am not actually adding them to the DB (want to distinguish them from real bills still in DB), not yet calculating additional bills for monthly or quarterly (so not adding them to DB either), then interface would need to show/hide real vs auto-filled bills. To note growth only takes into account real bills, BUT, it also only calcs growth on consecuttive full year data sets - e.g. years with quarterly bills for less than the full year are ignored for now
|
2025-08-18 17:49:36 +10:00 |
|
|
|
98fa17acd7
|
first pass of trying to work through deriving annual growth on bills, what info I need, etc. definitely not even close to finished
|
2025-08-18 11:14:21 +10:00 |
|
