Skip to content

Conversation

@CheChe903
Copy link
Member

No description provided.

@CheChe903 CheChe903 changed the base branch from main to develop December 28, 2025 05:38
Copy link
Collaborator

@Starlight258 Starlight258 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생하셨습니당 👍

Copy link
Collaborator

@2Jin1031 2Jin1031 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생했어요! 체체~

DocumentServiceJavaDocumentService 내로 포함시키는 건 어떨까요? 원래 코틀린 마이그레이션을 대비해서 분리했던 거라, 이번 PR에서 함께 정리하면 좋을 것 같습니다.

return ApiResponseGenerator.success(documentServiceJava.searchOrganizationDocument(uuid));
}

private <T> ResponseDto<List<T>> convertToResponse(Page<T> pageResponses) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

p2) 나중에 서비스 로직으로 들어가도 되겠네요~

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이건 유틸성이 강해보인다고 생각하는데 어떠신가용 ~?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

그르네요
DTO 형태는 서비스 책임이라고 생각해서 한 말이었는데 다시 보니 오해의 소지가 있을 수 있겠군요

convertToResponse는 유틸 클래스로 빼고,
DTO를 반환하는 결정을 서비스에서 끝내는 구조는 어떻게 생각하시나요~?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

좋습니다~ 현재 PR은 마이그레이션만 진행을 마치고 새로운 이슈로 파는 게 좋아보여서 머지할게요~

@CheChe903 CheChe903 merged commit 47ee6ee into develop Dec 28, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants