Block a user
5ca99ca1f4
update to note fortnightly pay dates are wrong on year rollover and so I am paying myself a week early at those times
4389045ed5
moved some hard-coded dates to top of calc.py for ease of use in multiple functions, but also just for code readability, they are more like constants than variables. Code now works out key_dates for use in dealing with future bills / next steps
b69ec82510
just made graph taller for now, might one day make it smaller or larger depending on whether we are comparing or not?
6ae1023f6e
removed debugs, add automatic annotations if bill amount is > $1000, factor in growth for ioniq6*, added debug too
c5cfc00793
put back ioniq 6 future bills, but use bill data to set values - assumption at present is they are yearly bills, could do better, but good enough for now. This commit also changes selects to return bill_type not bill_type_id and removed some debugs for bill amt in calc loop
ebac4aaf66
incorporate bills for dates/amounts into calculations, still need to do future bills on triggers
4b63b8bd44
complete the future bill handling, added new UI to match a need for it, also tighten up other TODO items
d80cffa0dd
fix up mistaken col-4 for wrong Date header, move from name to bill_type for new/update bill and support future dates by showing future in the text, rather than show an actual input type=date
2459dc6ea1
allow handling creating future bills - for when I quit, and will help with when switch to owning Ioniq 6
95d792e72f
added a set of titles when adding new bill / new bill types, allows to toggle date to be when quit or normal date, with normal date we use data, with when quit, we have growth we will use for simple growth and then date(s) can be factored in based on when I quit which is changable in the main financial data
f4490e937a
with dark mode, using info instead of primary feels easier on the eye and allows for consistency with graph colours
e373dd0009
Change approach with Qtr bills, all are simple based on last qtr - when we have normal Qtr bills (freq 'Quarterly') we just use last qtrs data for growth much easier. For GAS, we have the 'Quaterly (forced)' freq. which uses the forced/calc. amount per qtr for growth, its good enough for Gas bills - which dont always have 4 bills a year
3a5b77f12d
Change approach with Qtr bills, all are simple based on last qtr - when we have normal Qtr bills (freq 'Quarterly') we just use last qtrs data for growth much easier. For GAS, we have the 'Quaterly (forced)' freq. which uses the forced/calc. amount per qtr for growth, its good enough for Gas bills - which dont always have 4 bills a year
c74383f89e
added a commented out simple debug of totals to help understand bills for now - prob will make this into real table somehow in future
07f2a321ec
added support for Quarterly (seasonal) and Quarterly (fixed), also updated live DB to match
2937866617
improve how we find monthly bill in a month, dont use exact date just use yy-mm, also fix BUG where kayo used estimate in jan to project for the next 5years, rather than real bill in feb (all in the future) to estimate
4c96a9b576
with monthly bills and < 12 in first year, wont have full yr total so cant do simple growth - fix for this
24c581a35a
use totals to calc bill totals - should be less work, also improved cosmetics of totals display
c41048ab82
made lhs wider, shrank rhs, put this_year total per bill type in lhs, altered totals formatting at bottom
7422321227
call calc_future_totals to pass data onto html so we can show per bill type annual amount in this year
338b63aa06
now the UI shows annual costs, updated the comments and bills figure again to be more accurate
de32bdc7ff
now have a calc_future_totals func that is used to allow html to show the bills as a simple annualised cost per year
e84faffd79
when choosing a Tab, make the new bill drop-down be of that type. When we save a new bill, change the last-tab to be the type of bill we just added
2bdd1348b8
fixed a few bugs, annual growth was just broken, dont add another estimate bill when we have one for that year or in that quarter, removed lots of debugs, fixed a few bugs where the first data point in a new year/qtr would not have arrays initialised properly first, apportion quarterly data in future real bills - it happens with Rates
91ebc227b6
add support for simple growth, also remove all estimated bills when we add a new real bill
89fe874c5c
added simple growth, changed column widths and header formats to work better. Added a quick and dirty Total bills in 2025 section
89d58e4cd3
fixed a few logic bugs with quarterly data, now accurately puts bill proportions into relevant quarters and estimates future bills based on quarterly data - all works so far
f3b828b051
well, calculated proportioned per quarter values - not making much difference on growth numbers, BUT, will now be able to project future estimates based on full quarter cost, not just a bill in that quarter that may only cover 2 months
4b5b713c20
hack to handle gass bills (for now), seems we have more than 4 for a quarterly cycle, and they are all over the shop/inconsistent. Added thoughts on how to tackle in TODO
1719032ebf
wrapped new_bill in new_estimated_bill func, that adds to DB and to local bill_info, use this better to fill in quarterly future bills. Also exclude in growth calculations the final year of real bill if it includes estimates and real figures. For now, this is usable
b05f7b05e8
now remembers ui values for which tab we are on and whether we clicked show estimated or not