ElevatEd-Devs/ElevatEd_backend

AI Summary: Develop an authentication endpoint for updating user passwords. This includes modifying the existing signup endpoint to store new password hashes in the `user_password_history` table, ensuring that email updates also trigger this storage.

AI Summary: Create an API endpoint that validates user passwords against several criteria: minimum length (8 characters), alphanumeric and special character composition, and a five-cycle reuse prevention.

AI Summary: Create a REST API endpoint that retrieves a user's course data from a PostgreSQL database. The endpoint should initially return only course information and will require future implementation of user authentication (likely using bearer tokens).

AI Summary: Create a RESTful API endpoint for managing assessments. The endpoint should support Create, Read, Update, and Delete (CRUD) operations for assessment data, but will not include grading functionality. Future considerations include user authentication via bearer tokens.

AI Summary: Design and implement an authentication API endpoint that interacts with a Postgres database to handle user login, session management (including automatic logout), and manual logout. The initial phase focuses on fetching user data and session tracking. Future phases will include calendar syncing, email functionality, account deletion, MFA, and restricted account creation.

AI Summary: Create a REST endpoint that handles auto-grading and manual grade entry for assessments. The endpoint should accept the assessment ID as a URL parameter, update grades in a PostgreSQL database, and include robust error handling with database rollback on failure. Future iterations will require user authentication via bearer tokens.

AI Summary: Create a RESTful API endpoint for managing events, supporting CRUD operations (Create, Read, Update, Delete). Future considerations include implementing user authentication via bearer tokens.

AI Summary: Create a RESTful API endpoint for managing appointments, allowing users to create, read, update, and delete appointments. The endpoint must include user authentication, likely using bearer tokens.