2023-05-01 - Food Delivery App

main topics

MVC
Router
CSV
Inheritance

My Mental Model for MVC

MVC is not only Model-View-Controller, it also has a router (and an app.rb to instantiate and run the router.

app.rb: instantiates and run the router
router needs a controller (one or more)
controller
1. needs a repository
2. instantiates a view
repository needs a file (to act as a database)

Food Delivery - Day 2

Note

Common question: why are we spreading our software across several different files?

The answer is: software MUST be easy to change.

That's what the term soft in soft-ware means. As opposed to hard-ware.

So, we are creating all this different files so we can make our software easier to change, even if sacrificing the easiness to write. Of course we want easier ways to write software, but making it easier to change is a priority.

create employee model
- @id
- @username
- @password
- @role (manager or driver)
test in app/test.rb
create employee_repository
- @csv_file
- load_csv
create fake data in employees.csv (a manager and a driver)
test in app/test.rb
create a sessions_controller
- login
  - ask username
  - ask password
create a sessions_view
- ask_for
in the router, add sessions_controller
- in #run, call @sessions_controller.login before print_menu
adjust app.rb
test the login calling the app.rb
back to sessions_controller
- login
  - employee = @employee_repository.find_by_username
  - check employee for username/password match
    - success: @view.signed_in and returns the employee
    - failure: @view.wrong_credentials and calls login again
back to router
- after login, display manager or driver menu
back to employee model
- create #manager?
back to router
- create manager_menu
- create driver_menu
- create manager_action
- create driver_action
- create a logout! method
- call logout! in the #quit!

Recommended flow

code the model
- test it in test.rb
code the repository
- test it in test.rb
code the controller and the view
- test using the router