Add pagination support to GetAllUserPostQueryService and provide corresponding integration test

[zigzagdev]

Why

The existing implementation of GetAllUserPostQueryService returned all posts associated with a given user without any pagination logic. For scalability and performance, especially when dealing with a large volume of posts, pagination is essential.

What

• Refactored the getAllUserPosts method to accept $perPage and $currentPage parameters.
• Integrated Laravel's built-in paginate method to fetch paginated user posts.
• Adapted the result to a PaginationDto, mapping each post to a domain entity via PostFromModelEntityFactory.
• Updated the paginationDto() method to handle pagination metadata (e.g., total, current_page, per_page, etc.).
• Added integration tests that:
  • Insert 50 dummy posts with controlled timestamps.
  • Fetch the first and second pages using the service.
  • Assert the expected size and content of the paginated result.

[Copilot]

Pull Request Overview

This PR refactors GetAllUserPostQueryService to support paginated queries and updates related interfaces and DTOs, along with adding integration tests to verify the new behavior.

• Service now accepts $perPage and $currentPage, uses Laravel’s paginate, and maps results to a PaginationDto.
• The interface signature was updated to match the new pagination parameters and return type.
• Pagination DTO was expanded (with corrected from and to types) and integration tests were added to seed posts and assert pagination metadata.

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File	Description
src/app/Post/Infrastructure/QueryService/GetAllUserPostQueryService.php	Updated service to accept pagination params, use paginate(), and return PaginationDto
src/app/Post/Infrastructure/InfrastructureTest/GetAllUserPostQueryServiceTest.php	Added integration tests for pagination with dummy posts
src/app/Post/Application/QueryServiceInterface/GetAllUserPostQueryServiceInterface.php	Updated interface method signature and return type for pagination
src/app/Common/Application/Dto/Pagination.php	Changed from/to from string to int and expanded constructor parameters

Files not reviewed (1)

• .idea/workspace.xml: Language not supported

Comments suppressed due to low confidence (3)

src/app/Post/Infrastructure/InfrastructureTest/GetAllUserPostQueryServiceTest.php:35

• The createDummyPosts method is defined but never invoked, so no posts are inserted for the tests. Consider calling createDummyPosts (and refresh) in setUp to seed posts before each test.

parent::setUp();

src/app/Post/Infrastructure/InfrastructureTest/GetAllUserPostQueryServiceTest.php:116

• Test coverage is missing an assertion that the number of items in getData matches the requested perPage. Consider adding an assertion like $this->assertCount($this->perPage, $result->getData()); to verify page size.

        }

src/app/Common/Application/Dto/Pagination.php:11

• [nitpick] Adding a PHPDoc block to explain the purpose of each constructor parameter would improve readability and maintainability of the Pagination DTO.

          private array $data,

[Copilot]

[nitpick] Consider renaming paginationDto to buildPaginationDto to better reflect that this method constructs a PaginationDto from raw data.

Suggested change

	return $this->paginationDto($userPosts->toArray());
	}
	private function paginationDto(
	return $this->buildPaginationDto($userPosts->toArray());
	}
	private function buildPaginationDto(