# Week7-BGJK  --- ## Project brief (G) Build a REST API that delivers FAC19 icebreakers, inspired by the morning check-ins and afternoon checkouts.  --- ## Workflow (G) ### Day 1 1. Conceptualising the API in Miro 2. Setting up the database 3. Setting up the routes/server --- ### Day 2 1. Finished questions and answers endpoints 2. Authenticating the user's details (mob programme together as a group) 3. Deploying to Heroku --- ## Structuring our database (L) ### Creating the schema: - Made up of three tables ```javascript= CREATE TABLE users( id SERIAL PRIMARY KEY, username VARCHAR(255) NOT NULL UNIQUE, password VARCHAR(255) ); CREATE TABLE questions( id SERIAL PRIMARY KEY, user_id INTEGER REFERENCES users(id), question TEXT NOT NULL ); CREATE TABLE answers( id SERIAL PRIMARY KEY, user_id INTEGER REFERENCES users(id), question_id INTEGER REFERENCES questions(id), answers TEXT NOT NULL ); ``` --- # Building our API (L) --- ### What does our API do? - Allows users without an account to view a database of icebreakers - View the answers associated with each icebreaker question - Authenticated users can also: - post answers - update answers - delete their answers --- ### API and its endpoints - ```/users``` : lists all users ```javascript= { id: 1, username: "Gio" }, { id: 2, username: "Camboi" }, { id: 3, username: "lizzy" }, ``` --- - ```/answers```: lists all answers and the user id/question id associated with each answer ```javascript= { id: 1, user_id: 1, question_id: 1, answers: "Surveillance Capitalism" } ``` --- - ```/answers/:id```: lists a specific answer based on id ```javascript= { answers: "Surveillance Capitalism" } ``` --- - ```/questions```: lists all questions ```javascript= { id: 1, user_id: null, question: "What book would you add to the school curiculum?" }, { id: 3, user_id: 8, question: "If you could genetically engineer your kids what traits would you give them?" } ``` --- ## What we learned - Difference between imports and require (imports not supported in node) - Making the most of SQL and its functionality - Example ```sql UNIQUE ``` --- ## What we learned continued... - A lot about not testing - Not thinking of the endpoints as frontend web pages, rather... - Abstracting the API - Can see JSON in browser. Not sure --- ## What we struggled with - Conceptualising the project without a front end!!!  --- ## Still confused about - What each API function does -- (more comments in code, writing ReadME sooner may have helped, clearer planning on what we want them to do) - What all the id's do! ``` /answers/:id /questions/:id /users/:id ``` -- should have used different names --- - What status codes to use when. Especially when to use   --- # It's Q&A time  ---