Chores Minutes 30 03 2020

30/03/2020 Attendees: Logan, Ryan, Vanessa, Aziz, Sam, Jaedyn, Sean, Jake, Will, Marc

• Backend seems overengineered
• Flats is a database where you can add or remove things from
• Chores should be identical as a database that you can add or remove
• Boilerplate code could be copied from Flats
• We should decide how much work we should
• Target at very least: have the chores working (input and output chores)
• Discuss common understanding for chores

Backend

• Ignore interfaces and helpers
• Mappings need to add one line - relates models to the DTO in both directions
• What is important: Controllers (these are where the endpoints are defined)
• Models (data class)
• They’ve already made a model class for chroes
• DTOs help serialise and send things over network
• Repository?
• We need to decide on endpoints and add controllers to the endpoints
• Make a repository for chores
• And update the chores model if appropriate
• We already have payments

Chores

• Weekly
• You have a chores table each week
• Monday to Sunday
• For Time, frontend shouldn’t interact or care about it, backend should calculate if a chore is needed per date
• In database, store every chore with the data, then API request fetches all the chores with the date
• ID to chores
• We need to define what our chores will look like
• If chores repeat every week
• One-off chore by default, but when reccurring ones can just be inserted? Not very clean
• Weekly chores by default, then add one-offs as an extra implementation
• So maybe multiple tables; 1 for weekly, 1 for daily, 1 for monthly, 1 for one-off chores
• Most chores are weekly?

Deliverables

• Product designers to design
• Get all design done, then next meeting (tomorrow) get at least 1 frontend and 1 backend to decide on backend x frontend API interaction with what we should get done

Minimal scope:

• Add chores
• Assign chores to people
• Weekly view?
• Mark chores as done
• Delete chores