-
Notifications
You must be signed in to change notification settings - Fork 0
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 #77 영수증 수정 기능 추가 #78
Conversation
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.
고생 많으셨습니다 !
|
||
public interface ReceiptUseCase { | ||
void save(ReceiptDTO.Save dto); | ||
|
||
void update(Long reciptId, ReceiptDTO.Update dto); |
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.
영수증 아이디 변수명이 reciptId로 되어있는데 의도하신걸까요 아니면 오타일까요 ??
만약 오타가 맞다면 receiptId로 수정해주시는게 좋아보입니당
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.
수정했습니다!
public void update(ReceiptDTO.Update dto){ | ||
this.updateUpperClass(dto); | ||
} | ||
|
||
public void updateUpperClass(ReceiptDTO.Update dto) { | ||
this.description = dto.description(); | ||
this.amount = dto.amount(); | ||
this.date = dto.date(); | ||
} |
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.
데이터 전달을 ReceiptDTO.Update dto로 객체로 사용해서 분리해준 점이 좋습니다
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.
updateUpperClass를 따로 분리해서 작성하신 이유가 있을까요?
Receipt는 별도의 상속 관계를 지니지 않아서 굳이 분리할 필요는 없어 보여요!
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.
구현하시느라 고생하셨어요! 로직에는 문제가 없어 보여요
@convert(converter = FileListConverter.class)
private List images;
이 부분은 더 이상 사용을 하지 않기 때문에 제거 부탁드릴게요!
그리고 PR 명 컨벤션에 맞게 수정 부탁드려요!
@NotNull Integer amount, | ||
@NotNull LocalDate date, | ||
@NotNull Integer cardinal, | ||
@Valid List<FileSaveRequest> files |
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.
의도하지 않은 null을 막기 위해 @Valid List<@NotNull FileSaveRequest> files
로 작성하는 것은 어떨까요?
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.
알겠습니다! 수정하겠습니다
public void update(ReceiptDTO.Update dto){ | ||
this.updateUpperClass(dto); | ||
} | ||
|
||
public void updateUpperClass(ReceiptDTO.Update dto) { | ||
this.description = dto.description(); | ||
this.amount = dto.amount(); | ||
this.date = dto.date(); | ||
} |
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.
updateUpperClass를 따로 분리해서 작성하신 이유가 있을까요?
Receipt는 별도의 상속 관계를 지니지 않아서 굳이 분리할 필요는 없어 보여요!
PR 내용
PR 세부사항
관련 스크린샷
주의사항
체크 리스트