Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Profile Info Route from Koa to NestJS #2394

Open
valerydluski opened this issue Jan 7, 2024 · 0 comments
Open

Migrate Profile Info Route from Koa to NestJS #2394

valerydluski opened this issue Jan 7, 2024 · 0 comments
Assignees
Labels
🚧 in-progress Work In Progress

Comments

@valerydluski
Copy link
Contributor

Objective

The goal of this ticket is to migrate the existing profile information route from the Koa framework to NestJS. This involves refactoring the code to be compatible with NestJS and ensuring all functionalities remain intact.

Current Implementation

The current implementation of the profile information route can be found in the GitHub repository: Profile Info Route. This file includes the necessary code and logic implemented using the Koa framework.

Tasks

  1. Analyze Current Koa Implementation: Review the existing Koa route to understand its functionality and dependencies.
  2. Refactor Code to NestJS: Convert the Koa-specific code to NestJS. This includes adapting middleware, request handling, and response mechanisms to the NestJS framework.
  3. Ensure Compatibility with Existing Services: Verify that the new NestJS route integrates seamlessly with other parts of the application.
  4. Testing: Thoroughly test the new NestJS route to confirm that it maintains all the functionalities of the original Koa implementation. Pay special attention to error handling and edge cases.

Acceptance Criteria

  • The route fully migrated to NestJS with all functionalities intact.
  • Successful integration with the existing system.

Notes

  • Please ensure to follow the NestJS best practices for route implementation.
  • Coordinate with the team responsible for the overall application architecture to ensure compatibility.
@valerydluski valerydluski self-assigned this Jan 7, 2024
@valerydluski valerydluski added the 🚧 in-progress Work In Progress label Jan 7, 2024
@valerydluski valerydluski moved this from Todo to In Progress in RS School App Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚧 in-progress Work In Progress
Projects
No open projects
Status: In Progress
Development

No branches or pull requests

2 participants