dac00p / tablegetter Goto Github PK

• Will need reservation response actions for the successful creation or updating of a reservation and review
• Review response actions are mis-labelled as reservation response actions

• Should datetime column be a string? Not sure, but datetime might be a reserved word in postgres.
• Reservations and Reviews: description column type should be text not string
• Join tables: naming convention is snake_case

• Don't work from back-end to front-end, bring one feature at a time all the way through the process. Start with reservations, get the back-end set up, then the flux architecture on the front-end. After that, go through the same process with reviews, etc. Restructure the timeline to match this process.
• Don't leave styling to the end - do it in parallel with the above process. A feature should not be checked off the list until it is sufficiently styled.
• Overall, looks good!

WTF, fix this!

• User and session routes should be namespaced under API. We require front-end auth and single-page apps.
• Reservations and Reviews: avoid deeply nested routes. For example, just make a GET request to /api/reviews and pass in params to indicate which restaurant you wish to query

deleted secrets yaml from local AND public...fix this?