Centralize Route Protection for Task Mutation Endpoints#222
Open
ash1shkumar wants to merge 1 commit into
Open
Conversation
|
@ash1shkumar is attempting to deploy a commit to the shreemp194-gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
👋 Thank you for opening this pull request! I will review your changes and assist you soon. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📝 Description
This PR refactors the task routing layer by centralizing authentication handling for all mutation endpoints. Previously, authorization middleware was attached individually to each protected route, which increased duplication and made future route maintenance more error-prone.
The updated implementation introduces a dedicated protected routing flow, ensuring that all task modification operations consistently pass through the same authentication mechanism.
Key Improvements
Impact
This change strengthens routing consistency and provides a cleaner foundation for future task-related endpoints while preserving existing functionality.
🎯 Type of Change
✅ Testing
Fixes #221
Expected Labels
level3NSoC'26