Skip to content

Milestones

List view

  • Purchase process

    Due by May 27, 2024
    •13/13 issues closed
    100% complete0 open13 closed

  • Product Management

    Deliver APIs for product creation and manipulation by the Vendors.

    Due by May 17, 2024
    •16/16 issues closed
    100% complete0 open16 closed

  • Authentication and RBAC

    Finish Backend Authentication and Role-Based Authorization module

    Due by May 6, 2024
    •20/20 issues closed
    100% complete0 open20 closed

  • Chores

    Tasks: **1. Project Initialization** - [ ] Initialize a new Node.js project using `npm init` or `yarn init` - [ ] Set up TypeScript configuration by creating a `tsconfig.json` file - [ ] Install required dependencies (e.g., Express.js, TypeScript, TypeORM, etc.) - [ ] Create a test API endpoint (`/status`) that returns json **2. Linting and Formatting** - [ ] Set up ESLint for code linting - [ ] Configure Prettier for code formatting - [ ] Create `.eslintrc` and `.prettierrc` configuration files - [ ] Add lint and format scripts to `package.json` **3. Testing** - [ ] Set up a testing framework (e.g., Jest) - [ ] Configure Jest for TypeScript - [ ] Create a `__tests__` directory for unit tests - [ ] Add test script to `package.json` **4. Database Integration** - [ ] Set up TypeORM for database integration - [ ] Configure TypeORM with the desired database (e.g., PostgreSQL, MySQL, or MongoDB) - [ ] Define entity models for the e-commerce domain **IGNORE THIS:** 5. _Authentication and Authorization_ - [ ] Implement user authentication using JWT or sessions - [ ] Set up role-based access control (RBAC) for authorization **6. API Documentation** - [ ] Set up Swagger or another API documentation tool - [ ] Document API endpoints, request/response payloads, and authentication requirements **7. Continuous Integration (CI)** - [ ] Set up a CI pipeline (e.g., GitHub Actions, Travis CI, or CircleCI) - [ ] Configure the CI pipeline to run tests, lint, and build the project **8. Test Coverage** - [ ] Set up code coverage reporting (e.g., Istanbul or Coveralls) - [ ] Add a code coverage badge to the project's README **9. README** - [ ] Create an appealing README file - [ ] Include project description, installation instructions, and usage examples - [ ] Add badges for build status, test coverage, and code quality **10. Environment Configuration** - [ ] Set up environment variables for different environments (e.g., development, staging, production) - [ ] Use a tool like `dotenv` to manage environment variables **11. Error Handling** - [ ] Implement a global error handling middleware - [ ] Define error codes and messages for common error scenarios **12. Logging** - [ ] Set up a logging library (you can use Morgan) - [ ] Configure logging levels and output destinations

    Due by April 26, 2024
    •14/14 issues closed
    100% complete0 open14 closed