Closed erikbern closed 5 years ago
no reason to have to set now explicitly going forward
now
another minor fix that came up
Coverage increased (+1.07%) to 97.861% when pulling d3d05e36c49196d94f1f394eedfc5f45b5888295 on timezones into 263690c94d97ef2455cdb718457fbcecc21ce9b7 on master.
realized this bug wasn't fixed, my test code was broken. will fix later.
kind of silly that this is 40 lines of test for 3 lines of code, but whatev
no reason to have to set
now
explicitly going forwardanother minor fix that came up