Skip to content

0.5.0

Compare
Choose a tag to compare
@jantman jantman released this 28 Oct 11:40
· 531 commits to master since this release
0.5.0
ef46452

This release includes database migrations.

  • Issue #118 - PR to fix bugs in the wishlist dependency package, and vendor that patched version in under biweeklybudget.vendored.wishlist.

  • Issue #113 - vendor in other git requirements (ofxclient and ofxparse) that seem unmaintained or inactive, so we can install via pip.

  • Issue #115 - In Transactions view, add ability to filter by budget.

  • Change BiweeklyPayPeriod class to never convert to floats (always use decimal.Decimal types).

  • Issue #124 - Major changes to the ofxgetter and ofxbackfiller console scripts; centralize all database access in them to the new biweeklybudget.ofxapi.local.OfxApiLocal class and allow these scripts to function remotely, interacting with the ReST API instead of requiring direct database access.

  • Issue #123 - Modify the Credit Payoffs view to allow removal of Increase and Onetime Payment settings lines.

  • Issue #131 - Add better example data for screenshots.

  • Issue #117 and #133 - Implement and then revert out a failed attempt at automatic balancing of budgets in the previous pay period.

  • Issue #114

    • Add transfer_id field and transfer relationship to Transaction model, to link the halves of budget transfer transactions in the database. The alembic migration for this release iterates all Transactions in the database, and populates these links based on inferences of the description, date, account_id and notes fields of sequential pairs of Transactions. (Note: this migration would likely miss some links if two transfers were created simultaneously, and ended up with the Transaction IDs interleaved).
    • Identify transfer Transactions on the Edit Transaction modal, and provide link to the matching Transaction.
    • Add graph of spending by budget to Budgets view.
  • Issue #133 - Change BiweeklyPayPeriod model to only use actual spent amount when creating remaining amount on payperiods in the past. Previously, all pay periods calculated the overall “remaining” amount as income minus the greater of allocated or spent; this resulted in pay periods in the past still including allocated-but-not-spent amounts counted against “remaining”.