Fix(backend): Updated README.md

Feat(backend): update deps

backend/README.md

@@ -1,4 +1,3 @@
-<<<<<<< HEAD
 # Backend Technical Write-up
 
 ## Steps
@@ -16,16 +15,6 @@
 
 `blueprint`: a collection of route handlers/API functionalities.
 
-## API route trailing slashes
-
-API paths should end with a slash i.e: `/sessions/` rather than `/session`.
-This is because requests sent to `/sessions` will be redirected to `/sessions/` whereas `/sessions/` won't get redirected.
-
-## Difference between database schema and database model
-
-- A schema defines the structure of data within the database.
-- A model is a class that can be represented as rows in the database, i.e ID row, age row as class member.
-
 ## Managing user's sessions (Authentication)
 
 - Login should results in a cookie being set in the user's browser, which is being sent in every subsequent request.
@@ -35,11 +24,6 @@ This is because requests sent to `/sessions` will be redirected to `/sessions/`
 ## Idempotent routes
 
 Idempotence is a property of a route where the final state is achieved no matter how many times the route is called, that is, calling the route once or 10 times has the same effect. This is a useful property as it means the route can be safely retried if the request fails. For RESTful and HTTP APIs, the routes using GET, PUT, and DELETE verbs are expected to be idempotent.
-||||||| 3c78fe9
-=======
-# Backend Technical Write Up
-
-## General Bits of Information
 
 ### SameSite setting
 
@@ -53,10 +37,6 @@ Pydantic is to validate the schema/the shape of our input/output (works with JSO
 
 Class full of data. Meant to be used to serialize data into JSON objects.
 
-### Quart specific terminologies
-
-`blueprint`: a collection of route handlers/API functionalities.
-
 ### API route trailing slashes
 
 API paths should end with a slash i.e: `/sessions/` rather than `/session`.
@@ -66,14 +46,3 @@ This is because requests sent to `/sessions` will be redirected to `/sessions/`
 
 - A schema defines the structure of data within the database.
 - A model is a class that can be represented as rows in the database, i.e ID row, age row as class member.
-
-### Managing user's sessions (Authentication)
-
-- Login should results in a cookie being set in the user's browser, which is being sent in every subsequent request.
-  The presence and value of this cookie are used to determine whether the member is logged in, and which member made the request.
-- Logout results in the cookie being deleted.
-
-### Idempotent routes
-
-Idempotence is a property of a route where the final state is achieved no matter how many times the route is called, that is, calling the route once or 10 times has the same effect. This is a useful property as it means the route can be safely retried if the request fails. For RESTful and HTTP APIs, the routes using GET, PUT, and DELETE verbs are expected to be idempotent.
->>>>>>> master

backend/src/backend/blueprints/serving.py

@@ -1,7 +1,6 @@
-from quart import Blueprint, render_template, ResponseReturnValue
+from quart import Blueprint, ResponseReturnValue, render_template
 from quart_rate_limiter import rate_exempt
 
-
 blueprint = Blueprint("serving", __name__)
 
 

backend/src/backend/run.py

@@ -21,9 +21,9 @@ from quart_schema import QuartSchema, RequestSchemaValidationError
 # Each blueprint is a logical collection of features in our web app
 from backend.blueprints.control import blueprint as control_blueprint
 from backend.blueprints.members import blueprint as members_blueprint
+from backend.blueprints.serving import blueprint as serving_blueprint
 from backend.blueprints.sessions import blueprint as sessions_blueprint
 from backend.blueprints.todos import blueprint as todos_blueprint
-from backend.blueprints.serving import blueprint as serving_blueprint
 
 # For making sure error responses are in JSON format
 from backend.lib.api_error import APIError