This is the README for an Express backend assignment that requires you to implement the REST APIs for an E-commerce based on the Entity-Relationship Diagram (ERD) assignment. The ERD assignment should outline the data model, including the relationships and attributes of entities within the system. You are tasked with designing and documenting the REST APIs according to the ERD specifications.

This Express backend assignment involves building a RESTful API for an E-commerce. You are provided with an Entity-Relationship Diagram (ERD) assignment that outlines the data model, including the relationships and attributes of entities such as products, users, orders and admin roles.

Before implementing JWT authentication, you are required to create the basic CRUD (Create, Read, Update, Delete) operations for the entities based on the specifications provided in the ERD assignment. This section focuses on designing and implementing the core functionality to manage and interact with the specified entities.

For security, this API should implement user authentication using JSON Web Tokens (JWT). Each user should have a unique username and password OR broker authentication. Certain admin endpoints may require special privileges for access.

The minimum requirements of the project.

1. Products

• Attributes: ID, name, description, categories, variants/ sizes
• Get list of all products with/without pagination
• Get list of products, filtering (search) by: name, categories, variant
• Get a product by ID

2. Users

• Attributes: ID, first name, last name, email
• Sign up a new user (username, password, first name, last name, email)
• Sign in user with username/password
• Update user profile (first name, last name, email)
• Forget password request
• Change password (username, old password, new password)

3. Admin Special users with certain privileges

• Add a new product, update info of a product, remove a product
• Ban a user, unban a user

All API responses should be provided in JSON format. A typical response should include a status, data, and an optional message field. The status field should indicate the success or failure of the request.

The API should include comprehensive error handling with clear and informative error messages. Errors should be accompanied by appropriate HTTP status codes.

Developers should conduct unit tests and integration tests to ensure the reliability and correctness of the API. Instructions for running the tests should be provided in the project's documentation.

The API should be deployed before the DEADLINE