Auto-formatted the code using Prettier

Author: Austin-X

course-matrix/backend/src/controllers/departmentsController.ts

@@ -30,7 +30,7 @@ export default {
       res.status(200).json(departments);
     } catch (error) {
       console.error(error);
-      res.status(500).json({message: 'Internal Server Error'});
+      res.status(500).json({ message: "Internal Server Error" });
     }
   }),
-}
+};

course-matrix/backend/src/routes/userRouter.ts

@@ -1,12 +1,12 @@
-import express from 'express';
+import express from "express";
 
-import {handleAuthCode} from '../controllers/authentication'
-import {login, logout, session, signUp} from '../controllers/userController'
+import { handleAuthCode } from "../controllers/authentication";
+import { login, logout, session, signUp } from "../controllers/userController";
 
 export const usersRouter = express.Router();
 
-usersRouter.post('/signup', signUp);
-usersRouter.post('/login', login);
-usersRouter.post('/logout', logout);
-usersRouter.get('/confirm', handleAuthCode);
-usersRouter.get('/session', session);
+usersRouter.post("/signup", signUp);
+usersRouter.post("/login", login);
+usersRouter.post("/logout", logout);
+usersRouter.get("/confirm", handleAuthCode);
+usersRouter.get("/session", session);

course-matrix/frontend/src/app/dashboard/page.tsx

@@ -1,18 +1,18 @@
-import { AppSidebar } from "@/components/app-sidebar"
+import { AppSidebar } from "@/components/app-sidebar";
 import {
   Breadcrumb,
   BreadcrumbItem,
   BreadcrumbLink,
   BreadcrumbList,
   BreadcrumbPage,
   BreadcrumbSeparator,
-} from "@/components/ui/breadcrumb"
-import { Separator } from "@/components/ui/separator"
+} from "@/components/ui/breadcrumb";
+import { Separator } from "@/components/ui/separator";
 import {
   SidebarInset,
   SidebarProvider,
   SidebarTrigger,
-} from "@/components/ui/sidebar"
+} from "@/components/ui/sidebar";
 
 export default function Page() {
   return (
@@ -46,5 +46,5 @@ export default function Page() {
         </div>
       </SidebarInset>
     </SidebarProvider>
-  )
+  );
 }

doc/sprint0/product.md

@@ -78,6 +78,7 @@ A fully realized Course Matrix will include the following features and developme
 - **Intuitive User Interface**: A seamless and user-friendly design ensures users can easily navigate and utilize the platform without requiring extensive instructions.
 
 **Development Standards**:
+
 - **Rigorous Testing**: All code is thoroughly tested to address potential bugs and ensure functionality across all use cases.
 - **Feature Integration and Code Review**: New features are reviewed by at least two team members to ensure quality and consistency before being merged into the production environment, adhering to a structured code review process.
 

doc/sprint1/RPM.md

@@ -72,6 +72,7 @@
   - Generate timetable
 
 - Calendar customization features:
+
   - Add, update, and delete personal events from the user's calendar
   - Customize the personal calendar with colour-coding
   - Overlay course options over the user's current calendar
@@ -96,4 +97,5 @@ None
   - When users finish filling out the filtering options and click on the search button, the website should not take over 5 seconds to display all courses that fit the description
 
 ### 2.5 Dependencies and Limitations
+
 - None

doc/sprint1/iteration-01.plan.md

@@ -15,6 +15,7 @@
   - Develop software backend API and frontend UI to handle users' account registrations and authentications to ensure secured access to different pages
 
 - **Epic 2: Course Database**: Kevin and Austin
+
   - Create a course database schema to store all course offerings and course information
   - Develop software backend API and frontend UI to display all courses and course offerings information
 
@@ -36,6 +37,7 @@ In addition to their specific roles, all team members have a collective responsi
     - Define tasks and responsibilities for each team member
 
 - **Stand up meeting**:
+
   - Location: Online or in-person depending on members availability
   - Time: Every Tuesday from 12 pm to 1 pm, Friday and Sunday from 9 pm to 10 pm
   - Purposes

doc/sprint1/sprint-01-review.md

@@ -50,12 +50,13 @@ Furthermore, we laid the foundation for a timetable generator by enabling users
 - Build database schemas to store course information, course offerings and user accounts by Feb 9th 2025
 
   - `course` schema:
+
     - The `offerings` table should have columns for the Meeting Section, Session Offering, Day of Week, Start-End time, Location, Number of current enrollments, Max number of enrollments, Instructor
     - The `courses` table should have columns for the course code, name, breadth requirements, description, prerequisites, corequisites, and exclusions
     - The `corequisites` table should have columns to map each course_id with their corresponding corequisite course_ids
     - The `prerequisites` table should have columns to map each course_id with their corresponding prerequisite course_ids
     - The `departments` table should have columns to map each department to their code name as shown in the course codes
-  ![course schema](./images/course_schema.png)
+      ![course schema](./images/course_schema.png)
 
   - `account` schema (renamed: `auth` schema) :
     - The `users` table should have columns to store user account information: email, encrypted password, user_id