rachanavishwanath / smartsplit Goto Github PK

Frontend Routes:

• You will need a not-logged-in splash page route
• Excellent job

Backend Routes:

• What is the financial state of the logged in user?
• Lets talk about the additional details in our 1 on 1

Nice work!

• Delete the "forgot your password? Click here"
• Center the signup and login forms (like split wise)
• Don't let the email or password inputs appear until after a user begins to put in their name

Excellent work!!

• The users should have a friends key that points to the array of the id's of their friends (rather than a friends slice of state)
• Sub_category should not be nested - put it in a sub_category slice of state or the category slice of state, and store sub_category_ids as an array if ID's
• Have reference to the additional details in the expense slice of state
• Lets talk about how you will store expense information in our 1 on 1
• We can just have 1 modal key in the UI slice of state - with a value that is a string of the modal that is open

Excellent job!!!!

MVP List:

• Split Friending and Add Expense into two MVP's and add bullet points under each
• Hosting on Heroku - what is ib?
• You will build in errors as you complete each feature - have Transaction history and Comments be your last two MVP's (1. Friending, 2. Expenses, 3. Transaction History, 4. Comments)

Schema:

• A group is made up of multiple friends and one person can belong to multiple groups - does just having a friend_id on the groups table work for this behavior?
• I do not see paid_by on the expenses table
• I am confused by paid_by on the Expense Details Table - lets talk about this
• What is the sub_category_id?

• All Expenses Breaks the App
• When you are on user 2's page and you add an expense with user 1 it shows up on user 2's page. It is only there until you navigate away - but shouldn't be there at all
• Add the errors (for if a user tries to save without adding in a description or cost

Excellent work!