todo.org_archive

Archived entries from file /Users/zyoung/TimeTracker/todo.org

Add next_paydate() function to invoice

Returns dt for next payday, has to know some previous payday to calculate every second week, or maybe just `if now::week_num % 2` because we started invoicing at the end of week 1 in the new year.

Archived entries from file /Users/zyoung/TimeTracker/todo.org

Create utility for printing my invoices based on note.txt

This should open note.txt, parse it, and print out an invoice

Normalize jobs on parsing

Mcelhose –> mcel, McElhose –> mcel

Save invoiced entries to separate file

Write invoice and invoiced entries to an invoice file

Make config have nothing to do with IO

Right now it’s written around ConfigParser which is disk-specific IO. I think it can be rewritten around a dictionary; and so the caller picks their data layer and passes it off as a dictionary. For now, tests and generating invoices for Ken and FF, the data layer will be disk.

Make invoice for Ken, on 02/12/19

Invoice will be for last week (few hours) and this week (zero hours), pay period is 2/4 - 2/17

gen_invoice_task should create a pay-period specific file

Fix self-referential asserts in testWriteInvoice()

There are self-referential asserts in testWriteInvoice() that don’t really prove anything. This became apparent when changing self.net_30 to None in all the Invoice() instantiators. There’s a lot of date-time precision that’s kept in the written file that might be making testing harder.

Removed a lot of junk in testWriteInvoice() that had nothing to do with the test, which is just verifying that a file was written. All the exact-value assertions (especially dates and computed values) belong in other methods: testSendInvoice() and testPrintInvoicedEntries().

Add total to printed invoice for my own expectations of $$

Add grand total hours

Add wage to config to compute gross pay

Add different pay periods per Company

Finney Farm’s invoice was named with the 2-week convention that works for Ken’s invoicing. Maybe call this ‘invoicingperiod’. “every 2 weeks starting on Monday”… is waaay awesome, but also waaayyy beyond me and this program at this point. Simply defining the period per company is fine for now.