Ken Johnson caf348f189 made some big changes here. The schedule had a has_one relationship with the PTO model. That is a problem since we only get one result back. meaning, a user cant have multiple scheduled events. This has been fixed with the use of has_many within the PTO model. Now, in relation to the PTO section, the next changes to happen are to be a fully functional create action that allows an event to be schedule, the form and controller has already been created. Umm, also, a calendar has been added and when we get the results back from a call to the create event action we will update that calendar. Think that is about it for now

2013-05-28 12:48:35 -04:00

..

.gitkeep

made some changes to the application controller, added a user controller, and am now about to start working on the login piece

2013-04-24 18:09:43 -04:00

paid_time_off.rb

made some big changes here. The schedule had a has_one relationship with the PTO model. That is a problem since we only get one result back. meaning, a user cant have multiple scheduled events. This has been fixed with the use of has_many within the PTO model. Now, in relation to the PTO section, the next changes to happen are to be a fully functional create action that allows an event to be schedule, the form and controller has already been created. Umm, also, a calendar has been added and when we get the results back from a call to the create event action we will update that calendar. Think that is about it for now

2013-05-28 12:48:35 -04:00

retirement.rb

okay, so, we have associations rocking

2013-05-24 19:15:36 -04:00

schedule.rb

I am setting this up, in this way, so that we have some extensibility. We may wish to have some sort of a polymorphic association where multiple models need to have a scheduling model available to them. That being said, as of right now, only the pto model needs it so I am doing a belong_to and has_one association between the two

2013-05-27 13:09:33 -04:00

user.rb

added the PTO section

2013-05-24 20:54:07 -04:00