Merge application layer for handling post retrieval use cases #341
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 finalises and merges the
Application
layer logic responsible for coordinating post-related retrieval flows. It introduces theGetOthersAllPostsUseCase
, which delegates query operations to theGetPostQueryServiceInterface
, returning paginated data encapsulated in aPaginationDto
.This marks the integration of the application logic responsible for retrieving public posts made by users other than the currently authenticated one.
What’s Included
GetOthersAllPostsUseCase
:Handles input parameters:
userId
,perPage
,currentPage
Delegates query to
GetPostQueryServiceInterface::getOthersAllPosts
Returns
PaginationDto
composed ofPostEntity
instancesApplication-layer isolation:
No knowledge of Eloquent or database structure
Works purely with DTOs and interfaces
Supporting test (in separate PR or module):