Currently, when a user dislikes a blog post, the API response does not include the updated total number of dislikes. To enhance user feedback and engagement, and save computing power and cost, the backend should be modified to return the total number of dislikes for a blog post whenever a new dislike is added. This update will allow the frontend to display the updated dislike count immediately after the action is performed, improving the overall user experience.
Expected Behavior
When a user dislikes a blog post, the API response will include the updated total number of dislikes for that post.
Screenshots
Current response schema
Acceptance Criteria:
Stick to the changes required to fix the particular bug mentioned in description.
Do not change other people's code without appropriate permission.
Testing:
[ ] Write test for all updates requiring one
[ ] Ensure all existing tests passes [without tampering], alongside the new ones added
Description
Currently, when a user dislikes a blog post, the API response does not include the updated total number of dislikes. To enhance user feedback and engagement, and save computing power and cost, the backend should be modified to return the total number of dislikes for a blog post whenever a new dislike is added. This update will allow the frontend to display the updated dislike count immediately after the action is performed, improving the overall user experience.
Expected Behavior
When a user dislikes a blog post, the API response will include the updated total number of dislikes for that post.
Screenshots
Current response schema
Acceptance Criteria:
Testing: