Skip to content

Milestones

List view

  • Overdue by 1 year(s)
    Due by May 30, 2024
    12/12 issues closed
  • Overdue by 1 year(s)
    Due by May 30, 2024
    9/9 issues closed
  • Deliver APIs for product creation and manipulation by the Vendors.

    Overdue by 1 year(s)
    Due by May 17, 2024
    16/16 issues closed
  • Finish Backend Authentication and Role-Based Authorization module

    Overdue by 1 year(s)
    Due by May 6, 2024
    19/19 issues closed
  • Tasks: **1. Project Initialization (AMBROISE Muhayimana)** - [ ] Initialize a new Node.js project using `npm init` or `yarn init` - [ ] Set up TypeScript configuration by creating a `tsconfig.json` file - [ ] Install required basic dependencies (e.g., Express.js) - [ ] Create a test API endpoint (`/status`) that returns JSON **2. Linting and Formatting (Eddy)** - [ ] 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 (Leo Rurangwa)** - [ ] 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 (Bertrand Shema)** - [ ] Set up TypeORM for database integration - [ ] Configure TypeORM with the desired database (We'll use PostgreSQL) - [ ] Define entity models for the e-commerce domain **5. API Documentation Set up** (Manzi Karenzi) - [ ] Set up Swagger or another API documentation tool - [ ] Document API endpoints, request/response payloads, and authentication requirements **6. Continuous Integration (CI/DC) (Eric Niyibizi)** - [ ] 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 - [ ] Deploy the API **7. Test Coverage (Leo Rurangwa)** - [ ] Set up code coverage reporting (e.g., Istanbul or Coveralls) - [ ] Add a code coverage badge to the project's README **8. README** (Manzi Karenzi) - [ ] Create an appealing README file - [ ] Include project description, installation instructions, and usage examples - [ ] Add badges for build status, test coverage, and code quality **9. Environment Configuration (Xavier)** - [ ] Set up environment variables for different environments (e.g., development, staging, production) - [ ] Use a tool like `dotenv` to manage environment variables **10. Error Handling (Bernard Niyomugabo)** - [ ] Implement a global error-handling middleware - [ ] Define error codes and messages for common error scenarios **11. Logging (Cedric Sangwa)** - [ ] Set up a logging library (you can use Morgan) - [ ] Configure logging levels and output destinations

    Overdue by 1 year(s)
    Due by April 26, 2024
    22/22 issues closed