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

Add updateStudentStatus Endpoint to Existing Student Controller in NestJS #2509

Open
6 tasks
valerydluski opened this issue Jul 12, 2024 · 0 comments
Open
6 tasks
Assignees

Comments

@valerydluski
Copy link
Contributor

Description

The updateStudentStatus route, currently implemented using Koa in this file, needs to be migrated to the existing student controller in NestJS. This addition will help standardize our backend framework and leverage NestJS's features for improved maintainability and scalability.

Objectives

  • Framework Migration: Transition the updateStudentStatus route from Koa to the existing student controller in NestJS.
  • Code Standardization: Ensure the new implementation follows NestJS conventions and best practices.

Tasks

  1. Route Migration:

    • Add a new updateStudentStatus endpoint to the existing student controller in NestJS.
    • Implement the updateStudentStatus method in the controller, ensuring it replicates the existing functionality.
  2. Service Layer Integration:

    • If not already present, create or update a service in NestJS to encapsulate the business logic for updating student status.
    • Ensure the controller calls the service method to update student status.
  3. Validation and Error Handling:

    • Implement appropriate validation for the input data in NestJS.
    • Ensure consistent error handling aligned with NestJS practices.

Expected Outcome

The updateStudentStatus route will be fully implemented in the existing NestJS student controller, maintaining all existing functionalities while benefiting from NestJS's modular architecture and improved code maintainability.

Additional Notes

Coordinate with the development team to ensure a smooth migration process. Regular code reviews and testing will be crucial to identify and address any issues early in the process. The existing Koa implementation can serve as a reference but should be deprecated once the migration is successfully completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants