Added a couple of failing tests. Need to figure out how to make these pass...
This test would never pass with all these function-call errors all over the place...
New Interval for your face
Some major DB changes around block reservations here, but now we're storing block bookings. Not reading them back yet though...
changed the manual test to make sure DB is populated correctly.
Filled out weekly interval and found a better way to skip to nearest day so back ported that into day of week.
This bug is WAT -worthy. Just changed a variable name halfway through a function. Bizzarro world.
I THINK that for block bookings, we'll need this new method. Gives consuming services a way to skip to the next period.
Added a friendly name to block reservations
BUGFIX: mis-spelt variable
added a block reservations factory for consistent method calls
BlockReservations weren't being populated on retrieval. Looks like this were the cause like.
Seemed like a good idea at the time. Removed some exceptions. They were intended to be a (strict!) guide to usage of the object, but turns out they killed reuse.
Should probably initialise all this stuff.
Added a method to block reservations to check overlap.
Merge branch 'blockbookings'