Service CRUD

[seixasfelipe]

A Service is a job that will be done by our cleaning team, it is actually what we sell to people, that's our core business.

When someone wants his car cleaned, he comes to our cleaner area with his car, choose what kind of tasks we must do ( basic wash and use wax for instance) and pay for the service.

Thus, the service is composed by:

• what vehicle
• what tasks (can be more than one)
• who is the customer (usually presented automatically because we know what vehicle)
• total price of the service
• other informations: * date of the service * any other relevant information that we would like to write down (i.e. do not use some detergent, must have be done until 5pm, be careful with rear mirror, etc)

For reference see: public/layout/servicos-todos.html

[fraga]

Guys I'm really noob on this so I am generating controllers and models by hand, I mean, not using scaffold, is this correct?

[fabianoalmeida]

@fraga it's correct. You could used scaffold without problem. I defined on application.rb configurations to generate only files we really use to build the application, when run rails generate scaffold .... Test it and see the result.

By the way, we defined here #15 that we'll consider use ServiceBundle and ServiceOrder, right? If I'm correct, why did you create a model with Service name?

[fabianoalmeida]

One doubt... We'll use order instead service_order, correct?

[fraga]

I think we need a model diagram so we don't get confused =)

[seixasfelipe]

Yes @fabianoalmeida, using order I think was the original idea when we decided to change task to item. But if it is better use service_order let's refactor and go on :)

[fabianoalmeida]

@seixasfelipe no, I'm ok with order, no problem. I'll take a look at the app and change the view to support all items in this issue and lastly close it. :pray:

[fraga]

We're half way on this milestone =)

[fabianoalmeida]

Oh yeah @fraga. I'm a little busy this week, but I'll try solve it until weekend.