Schema/API Design Comments (Jose Espinoza)

[joseespinoza15432]

1. add default values for frequency enum if possible. Potentially add a description to clarify the use more
2. potentially simply some of the constrains for clarity
3. add foriegn keys where applicable. I.E. if roomates or bills have a necessary relationship with each other
4. add default value for for duration_mins
5. In the api, describe eorror scenarios like 400 for bad requests etc.
6. In post/put endpoints, describe stricter validation fields like the frequency must match the enum value
7. Ensure proper status codes for the endpoints.
8. Ensure correct json response fields
9. RESTful naming convetions for the endpoints like POST /create_chore
10. Add unique constraints where you can to avoid duplicates
11. Add timestamps to track when records have been made or modified. Also include deletion timestams
12. Add composite keys where aplicable in supabase
13. normailze naming convention for the table definitions