Dev ticket backlog/things that need to be done

[prooflesben]

Frontend

• Make sure user page has the correct design
• Make sure pfps are showing correctly(CHeck prs)
• If you are logged in and there are no cookies show a pop up to logout the user and just say there has been an error(Still broken)
• Clean up the error showing for update profile
• Cashflow
  • Methods to calculate things (Mostly a project structure clean code thing)
  • Make it so you are able to check and uncheck certain cost or revenues to test out how the cashflow would look like without certain things
  • Graphs that combine all of the cost and reveunes and have them increase with the correspodning percentages
  • Only fetch the cashflow things if your role is an admin

Backend

• Cashflow
  • CRUD endpoints for both tables
    • Grant needs to be active to apply
  • POTENTIALLY: Method to get all the revenues from reveunue table and from the grant table(Could get all the grants and just size them down to being the structure of the revenue type)
• Make it so our emails don't go to spam

Misc

• Think about doing some code reviews to find some bad logic or just bad code I feel like we don't always do things the smoothiest

• Bug bash soon

• Cashflow

  • Figure out what needs to be in the store for the cashflow.
  • When porting the grants to reveunes make sure you only apply active grants
    • First have the grant only be editable in the grants page
    • Once that has been done edit the grant inplace using the grant id or something of the sort to edit the grant cash part of it

3/22-3/28 Tickets

• Update user page design
• Show logout prompt if the cookies are missing
• Connect revenue and cost to backend and display them in the card form and have it connect to the graph
  • Make it so that you also pull all the grants and then just downsize the grant info into a revenue(grants have to be active to count as reveune)
• Connect adding a cost and revenue to the backend with the frontend ui and add in input validation and error handling
  • Update the drpdowns with the enums defined in the middle ware
• Ensure the starting cash amount, salary, and benefits increase are uploaded to backend on logout
  • Make sure this is in the logout method