Open eddiem3 opened 9 years ago
Ya abstracting the barber and the client in separate model makes more sense then the user model that we currently have.
That's fine. To me, we can do whatever either ways with same level of difficulty.
Ok I'll go ahead with it then
On Wednesday, February 4, 2015, Ifeanyi Kalu notifications@github.com wrote:
That's fine. To me, we can do whatever either ways with same level of difficulty.
— Reply to this email directly or view it on GitHub https://github.com/eddiem3/live-chair/issues/17#issuecomment-72854637.
Eddie Massey III
Artificial Intelligence in Action Founder Low Country Judicial Merit Selection Committee Member Orangeburg County Democratic Party Web Developer Kingspromise.org Founder
Btw, this will also imply breaking the api into a V2. Have you guys started with the app already? If so you'll need to change the endpoint once this is done.
We haven't started yet... We begin this weekend.
Hey guys,
I think we should have a model for the barber and a model for the client and relate a an appointment between a barber and a client via a has many through relationship. To me it'll be easier to keep track of appointments this way.