created the boat migration
created a timeslots migration
created the migration for assignments
created the booking migration
created the models for the tables in the db
added validations to the models
started the first route, timeslot, to create the timeslots
added the rails-api gem to try to get around the demand for templates(thanks DHH :(). Have enough fuctionality available that I should be able to start creating objects using the testing app. However right now it is still pissy about the template issue. hopefully I can fix this soon
still havent managed to get rails to stop breaking due to a lack of views. I will think about this for a while and hopefully come up with some ideas for my next attempt. Need to get going for now.
finally figured out why things were broken. I missed a detail. applicationcontroller needs to inherit from api instead of base. now I need to make the objects actually be created, I missed something in my params handling
fixed the routing issue caused by overlapping namespacing by providing a different method name for the post routed
have the boats, timeslots, and assignment routes working. The visualiation tool appears to be broken. After looking at the source code I think that my program should currently be returning the correct api information, but I dont have any of the booking logic written yet. still plan on doing that last.
realized that some of my render json calls were missing the json: key and fixed them
switched from sqlite3 to postgress. dont know what I was thinking. only pg can handle array fields.
after some though, revamped the associations, but am having trouble accessing the relationships. Once I figure out why my associations are broken I need to add the associated boats to the reponse body of new_timeslot.Also corrected the problem with cors requests being rejectd
timeslot availibility is now updated when an assignment is saved. Next up is to reduce it when a booking is made and to validate whether or not there is space for a booking.
I am so close now. My validations are just slightly off in terms of the logic needed. There are some more wrinkles to iron out, but the basic structure is done. Hopefully I can nail down the logic soon and then write some tests. Since we had a testing suite available I chose not to tdd, but would like to do some unit testing and some other cases before I am satisfied
Merge pull request #1 from cdelauder/scheduler

Scheduler