-
Notifications
You must be signed in to change notification settings - Fork 263
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
Updated the logic to return 404 instead of 200 when wrong taskRequest Id is sent #2296
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add screenshot
Can you please check if we have tets written for this, if yes then how are they passing before |
Also can we please improve the title and PR description |
+1 |
Update the API Contract and link it here for the error codes and other changes. |
add tests SS |
Add test coverage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
catch block error message in the findTaskRequestById is not correct, can you please update it as well
updated the error message |
I have kept test coverage screenshot in the Description |
Real-Dev-Squad/website-api-contracts#207 API contract changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add unit test coverage for the fetchTaskRequestById()
Date: 14-12-24
Developer Name: akshat
Issue Ticket Number
(#2290 )
Description
When queried with taskRequestId which doesn't exist,
fetchTaskRequestById
was returningTasks returned successfully
instead ofTask request not found
, have changed the code to return the proper error message, currently there are no tests for this case, so it didn't get highlighted.Documentation Updated?
Under Feature Flag
Database Changes
Breaking Changes
Development Tested?
Screenshots
Current implementation returning 200 OK, even when the id is incorrect
Updated implementation to return `Task request not found` when wrong id is passed
Test Coverage
Screenshot 1
unit test coverage
Additional Notes