Design Docs

[darreneid]

Wiki Home Page

• [x] Is the first page you see upon entering the wiki
• [x] Contains a welcome message
• [ ] Contains a link/placeholder for a link to the live page
• [x] All links in the right sidebar should contain each wiki page and link to the correct page
• [ ] Correctly formatted
  • [ ] each wiki page is listed in bullet points
  • [x] all links route the correct page

    Comments

• Almost there - see checklist

  MVP Feature List

• [x] Should have 7 total features
  • [x] 3 of those are User Auth, Hosting, and Production README.
  • [x] The other 4 are unique to the specific app
• [x] Contains a description sentence of the app
• [x] Includes two to three detailed bullets on functionality and presentation of feature
• [x] Two CRUD features
• [x] Estimates how long it will take the code each feature
• [x] Correctly formatted
  • [x] Features are listed in an ordered list
  • [x] Each feature is broken down into bullet points

    Comments

• My initial reaction is to have expense CRUD be the first feature but it wouldn't make a ton of sense to do that without having relationships, so I see the logic
  • Does relationships encompass both friends and groups? Or just groups?
  • Would friends just be users I'm in a relationship with?
• Are bills equivalent to expenses?

• Recommend moving comments up to be your third feature and finishing with transaction history and search

  Database Schema

• [ ] Contains correct datatypes
• [x] Contains appropriate constraints/details
  • [x] primary key
  • [x] not null
  • [x] unique
  • [x] indexed
  • [x] foreign key
• [x] Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
• [x] foreign key and table name are lowercased, snake_cased, and back_ticked
• [x] Correctly formatted
  • [x] schema is written in a table format
  • [x] the table’s name are lowercased, snake_cased and back_ticked
  • [x] the table header column names are bolded
  • [x] columns names are lowercased and snaked_cased and back_ticked

    Comments

• Don't need to store image urls in the database
• See checklist
  • Foreign keys should have a bigint data type

  • Bill and debt amounts should be floats, I imagine

    Sample State

• [x] State shape is flat
• [ ] State’s keys are camelCased
• [x] All keys within the values in the state are accessible in the schema
• [x] Correctly formatted
  • [x] Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • [x] Top level slices
  • [x] entities
  • [x] session
  • [x] errors (here or in ui)
  • [x] ui (if needed)
  • [x] Should NOT have nested slices, aka comments inside of posts

    Comments

• See checklist

• Double check formatting, missing a few commas here and there

  Backend Routes

• [x] Contains the following sections: HTML, API Endpoints (Backend)
• [ ] Each route has a description
• [ ] API Endpoint routes contains wildcard variables written in snake_case
• [ ] Does not contain superfluous routes
• [ ] Have API routes that will allow the front end to get all info it needs and does not have unneeded routes

  Comments

• I'm happy to meet to talk through routing

  Frontend Routes

• [ ] Frontend routes contains wildcard variables written in camelCase
• [ ] Correctly formatted
  • [ ] Routes are displayed with inline coding text (backticks)

    Comments

• I'm happy to meet to talk through routing

[darreneid]

See above for feedback