FSP Checklist

[Carly-Schaaf]

Wiki Page Home

• [x] Is the first page you see upon entering the wiki
• [x] Contains a welcome message
• [x] 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
• [x] Correctly formatted
  • [x] each wiki page is listed in bullet points
  • [x] all links route the correct page

---

MVP List

• [x] Should have 7 MVPs.
  • [x] 3 of those are User Auth, Heroku, and Production README.
  • [x] The other 4 are from the MVP List or they have clarified them with you
• [x] Contains a description sentence of the app
  • [x] Includes the following list for the 4 app specific MVPs:
  • [x] Adequate styling
  • [x] Smooth, bug-free navigation
  • [x] Adequate and appropriate seeds to demonstrate the feature
• [x] At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• [x] Estimates how long it will take the code each MVP
• [x] Correctly formatted
  • [x] MVPs are listed in an ordered list
  • [x] Each MVP is broken down into bullet points

Comments

You need 2 more MVPs, at least one of those needs to be the production README you'll do on the last day. Will you have a search functionality for any of your MVPs? If so, you could make that your last MVP.

---

Database Schema

• [x] 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] Correctly formatted

  • [x] schema is written in a table format
  • [x] the table's name are back_ticked
  • [x] the table header column names are bolded
  • [x] columns names are lowercased and snaked_cased and back_ticked

Comments

You need to reformat your schema so that each of your tables are in actual table format (e.g. https://github.com/Carly-Schaaf/adventureBnB/wiki/Database%20Schema). You also need to include your db constraints as columns and model-level associations in comments below each table. Also - all tables should be pluralized.

User

• You need a session token and password digest.

Providers

• Do you want a type column here? It may be useful if you want to include a search functionality.

  Clinic

• address should be broken up into multiple rows (e.g. address_1, address_2, state, zipcode, country)

---

Sample State

• [x] State shape is flat!
• [x] 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
    • Some info from other tables is ok, for instance:
    • the author username and imageurl for a post. basically any info that the user can't change
    • like count and a boolean on whether the user likes the post instead of a likes slice

Comments

• Your scheduling and prescription slices of state should be nested under entities - remember, anything that comes from your db should be inside of entities.
• Your user and prescription data should be nested under the corresponding id, just as you do for appointments, shifts, etc.

---

Backend Routes

• [x] Contains the following sections: HTML, API Endpoints(Backend)
• [x] Each route has a description
• [x] API Endpoint routes contains wildcard variables written in snake_case
• [x] Routes does not contain superfluous routes
• [x] Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

Comments

• You need to have a full CRUD cycle for at least one of your MVPs. If you want a full CRUD cycle for appointments, you will need an edit and delete route. Also, your prescriptions update route is wrong (should be PATCH and have a wildcard).

---

Frontend Routes

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

Comments

• It looks like you're missing routes and have too many routes for appointments. For example, a "Create Appointment" page should be a single route - maybe appointment/new - and your appointment show page route should be something like appointment/:appointmentId. For clarity, I think you should nest each component under the route that will render it. Take a look at these routes for comparison: https://github.com/Carly-Schaaf/adventureBnB/wiki/Frontend%20Routes%20and%20Components.

[Carly-Schaaf]

Hey Trevor - looks like you're off to a good start! Read my comments above to update your proposal when you get a chance. Sorry to reference to my proposal so much, but I think an example could be useful. Feel free to ask any questions as a comment below - or slack me!