Implement API schema

[ecumene]

API Schema should be:

GET /project/{id}
POST /project
PUT /project
POST /project/{projectId}/walls

HTTP Method Examples:

• GET, POST, PUT, UPDATE, DELETE

• BROWSER localhost:3000/project = GET /project

• fetch (with GET) localhost:3000/project = GET /project

• fetch (with POST) localhost:3000/project = POST /project

• fetch (with DELETE) localhost:3000/project = DELETE /project

• fetch (with PUT) localhost:3000/project = PUT /project

GET /project/{id}

• Project name
• Project user details
  • Project creator name
  • Other stuff
• Other stuff

POST /project

• Create a project given a {"name": "Summer Project", "ownerID": 1}
• Return project (exactly like GET /project)

POST /project/{projectId}/walls

• Create a wall given a project ID and a wall length {"wallLength": 96, "isImperial": true}
• Would return wall info
  • Wall length
  • Any studs they have

1. Backend get a request with projectId, and Data
2. You'd get the wallLength and isImperial from Data
3. You'd calculate a list of values (stud numbers come from getListOfMeasurements)
4. You'd INSERT that into SQL into the "wall" table with your wall details (wallLength (integer), isImperial (boolean), listOfMeasurements (json))
5. Return the wall info back (id, wallLength, isImperial, listOfMeasurements)

[ecumene]

Try for next time: Make a POST for /projects and projects/{projectID}/walls

[JPM709]

Schema is partly implemented. As discussed in issue #40, API works top-down; create a user, get an ID -> use ID to create a related project, get back a project ID -> use projectID when posting walls. EDIT: created user is for show as of now; no cookies or anything yet. no returning user functionality.

[ecumene]

For Users:

/post -> /signup (Does not need auth)
/get -> /current_user (Does need auth)

[JPM709]

Still need DELETE project and walls.

[JPM709]

DELETE walls is done. Just need to DELETE project, then API is complete!