-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Refactor/#143] 어드민 API 요구사항 반영 및 오류 수정 #144
Conversation
7f5053e
to
6f23052
Compare
6f23052
to
fa01da5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
추가로 AddArticleResponse에서 AddArticleUseCaseOut를 참조하지 않고 값만 넘기도록 변경 필요합니다.
AddArticleResponse에서 AddArticleUseCaseOut를 직접 참조할거면 레이어 별 DTO 객체를 따로 정의할 이유가 없어요
val problemData: ProblemDetail | ||
val problemData: List<ProblemDetail> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
필드명이 복수형을 의미할 수 있도록 problems 등으로 수정되면 더 좋을거 같아요
private val problemDao: ProblemDao | ||
private val problemDao: ProblemDao, | ||
private val documentDao: DocumentDao, | ||
private val convertDocumentService: ConvertDocumentService, | ||
private val putDocumentService: PutDocumentService, | ||
private val getUrlService: GetUrlService |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
서비스는 도메인 별로 하나만 두는걸로 변경 필요합니다(저희끼리 정했던 부분)
추가로 유즈케이스가 아티클쪽인데 member, problem은 DAO 바로 사용하시나요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
여기는 어드민으라서 바로 dao로 사용했습니다!
domain 패키지가 web 패키지의 클래스를 알면 안된다고 생각하지만 |
#174 디스커션에 등록했습니다! |
🎫 연관 이슈
resolved: #142 #143
💁♂️ PR 내용
🙏 작업
🙈 PR 참고 사항
카테고리
📸 스크린샷
🤖 테스트 체크리스트