Prashasti assignment - #54
Open
Prashasti-Shrivastava wants to merge 3 commits into
Open
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
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.
testing:
Bugs:
Identified critical API bugs spanning routing, validation, and data mutation. Resolved Bug 1 (combining status filtering with pagination) and Bug 2 (1-based page offset logic) with full tests.
New route
added logic and route for assigning tasks and added tests for it
To do next
Rate limiting to prevent endpoint abuse/DDoS, and RBAC to restrict task creation, assignment, and deletion to authorized user roles.
what surprised me
How PUT requests performed a shallow merge ({ ...task, ...fields }) rather than replacing the resource, allowing clients to accidentally overwrite system fields like id and createdAt.
How PATCH /tasks/:id/complete was written to silently force priority back to 'medium', showing how state-transition endpoints can quietly introduce unintended data resets.
before shipping to production
Which production-grade database (e.g., PostgreSQL, MongoDB) are we migrating to, and is a load balancer configured for auto-scaling?
Are strict CORS policies set up for allowed origins, and is rate limiting enabled to block API abuse/DDoS?