[FEAT]: GET /api/v1/blogs/{blog_id}/engagement #1173
Closed
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 introduces an API endpoint to fetch engagement metrics for a specific blog post. The endpoint provides insights into a post’s popularity by tracking views, likes, comments, and shares.
Key Changes
GET /api/v1/blogs/{blog_id}/engagement
to retrieve engagement data.COUNT(*)
on indexed columns.API Response Example
Related Issue
#ISSUE1136
Motivation and Context
This feature enables blog authors and administrators to monitor engagement metrics, assess a post’s popularity, and support recommendation systems by identifying high-engagement content.
How Has This Been Tested?
✔️ Unit tests using pytest to verify:
✅ Successful retrieval of engagement data (200).
✅ Handling of non-existent blog posts (404).
✅ Efficient database read operations.
✔️ Mocked Redis caching and batch database updates using unittest.mock.MagicMock.
Screenshots (if applicable)
📊 Engagement metrics retrieved for a blog post.
Types of Changes
Checklist