-
Notifications
You must be signed in to change notification settings - Fork 1
[feat] BankAccountsDTO, CommentDTO, DecisionDTO 구현 #13
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
[feat] BankAccountsDTO, CommentDTO, DecisionDTO 구현 #13
The head ref may contain hidden characters: "feat/#9-BankAccountDTO-CommentDTO-DecisionDTO-\uAD6C\uD604"
Conversation
| @Getter | ||
| public static class DecisionRequestDTO{ // 특정 청첩장의 참석의사 조회 요청 DTO | ||
| @NotBlank(message = "청첩장 아이디는 필수입니다.") | ||
| private final String invitationId; |
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.
invitationId Long 타입 아닌가용??
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.
수정하겠습니다!
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.
방명록 조회할 때, 명세서에 pathvalue로 invitationId 받는 걸로 되어 있는데 requestDTO도 필요한가요??
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.
제가 혼동한 부분이 있는 것 같습니다! 해당 부분 수정하겠습니다
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.
이것도 pathvalue로 받는데 requestDTO 필요한지 궁금합니다!!
dyk-im
left a comment
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.
전반적으로 구성상 문제는 없습니다. 하지만 코드의 분리성을 생각하여 조금 다른 스타일로 가볼까 하는데 리뷰 한 번 읽어보시고 의견을 알려주세요!
src/main/java/com/wedit/weditapp/domain/comments/dto/request/CommentRequest.java
Outdated
Show resolved
Hide resolved
src/main/java/com/wedit/weditapp/domain/comments/dto/response/CommentResponse.java
Outdated
Show resolved
Hide resolved
src/main/java/com/wedit/weditapp/domain/decisions/dto/response/DecisionResponse.java
Outdated
Show resolved
Hide resolved
src/main/java/com/wedit/weditapp/domain/comments/dto/request/CommentRequest.java
Outdated
Show resolved
Hide resolved
src/main/java/com/wedit/weditapp/domain/decisions/dto/request/DecisionRequest.java
Outdated
Show resolved
Hide resolved
dogsub
left a comment
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.
동구와 위즈의 피드백이 훌륭해서 저는 더 말할 것이 없군요
| .content(comment.getContent()) | ||
| .build(); | ||
| } | ||
| } |
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.
requestDto는 서버에서 만드는 것이 아닌 프론트에서 변수명을 맞추어 보내는 형식이라 빌더 패턴과 참조 메서드 from 없이 getter, 매개변수 없는 생성자만 설정하면 된다고 합니다!!
| .phoneNumber(decision.getPhoneNumber()) | ||
| .addPerson(decision.getAddPerson()) | ||
| .build(); | ||
| } |
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.
여기도 마찬가지로 빌더와 참조 메서드는 없어도 될 듯 싶습니당
dyk-im
left a comment
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.
고생하셨습니다! 제가 요구한 부분 모두 수정되어 승인했습니다! RequestDto 들만 수정해주시면 감사하겠습니다!
wiz0208
left a comment
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.
수고하셨습니다~~
개요
�방명록, 참석의사 조회 관련 DTO를 작성했습니다.
BankAccountsDTO는 충돌 우려로 보류중이며,
이후 방명록과 참석의사 등록 관련DTO 작성할 예정입니다.
PR 유형
어떤 변경 사항이 있나요?
PR Checklist
PR이 다음 요구 사항을 충족하는지 확인하세요.
📣 To Reviewers