Refactor Student API: Improved Validation, Error Handling & Code Structure #82
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hanges in routes.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces multiple improvements to the Student API to enhance reliability, maintainability, and production readiness. The validation logic for the phone field has been updated to enforce a strict 10-digit numeric format using string validation, addressing previous limitations with numeric length checks. Error handling across all routes has been standardized, returning structured JSON responses with clear messaging. Redundant and duplicate code has been cleaned up for better readability, and the application now uses dynamic port configuration via process.env.PORT for deployment flexibility. Additionally, the /student route now supports optional query parameters, allowing for more flexible data retrieval. These changes collectively strengthen the API’s structure, improve data integrity, and prepare it for scalable use.