Feature retrieves total likes dislikes by author

[baydre]

Description

This PR implements a GET endpoint to retrieve the total number of likes and dislikes for all blog posts written by a specific author. The feature allows users to gain an overview of the total reactions (likes & dislikes) received by an author across all their posts.

Endpoint Details

• Method: GET
• URL: /api/v1/authors/{author_id}/likes-dislikes
• Functionality: Fetches the total count of likes and dislikes for all posts by a given author.

Request Example

GET /api/v1/authors/789/likes-dislikes

Success Response Example

{
  "status": "success",
  "message": "Likes and dislikes for the author retrieved successfully",
  "data": {
    "author_id": "789",
    "total_likes": 350,
    "total_dislikes": 25
  }
}

Error Handling Examples
Author Not Found

{
  "status": "error",
  "message": "Author not found",
  "data": null
}

Invalid Author ID

{
  "status": "error",
  "message": "Invalid author ID format",
  "data": null
}​

Related Issue (Link to issue ticket)

​Closes #1128

Motivation and Context

• ​Provides an overview of user engagement with an author’s content.
• Helps in tracking the author’s content performance across all blog posts.
• Ensures proper error handling when retrieving author-related statistics.

How Has This Been Tested?

​✅ Unit Testing:

• Implemented unit tests using pytest to validate the correctness of the endpoint.

✅ Manual Testing (Postman):

• Sent test requests to verify correct responses for valid, missing, and invalid author IDs.

✅ Database Validation:

• Queried the database to ensure that likes & dislikes are correctly aggregated per author.

✅ Test Environment:

• OS: Ubuntu 20.04
• Python Version: 3.10
• Database: PostgreSQL

Screenshots (if appropriate - Postman, etc):

​

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
  ​

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.