-
Notifications
You must be signed in to change notification settings - Fork 4
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]회원가입 기능 구현 #18
[Feat]회원가입 기능 구현 #18
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.
구우우욷
마커 인터페이스를 사용하는 이유가 궁금합니다 |
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.
toEntity를 converter로 따로 두는 이유가 있나요? dto를 entity로 변환하는데 toEntity는 dto를 entity로 변환해주는 것이니까 dto의 멤버함수로 있는게 좋지 않나요?
private final ValidNicknameService validNicknameService; | ||
|
||
@Transactional | ||
public void execute(final SaveUserRequest source) { |
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.
final을 쓰는 이유가 궁금합니다
public class ValidEmailService { | ||
private final UserRepository userRepository; | ||
|
||
public void execute(EmailSupplier supplier) { |
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.
supplier를 쓰는 이유? supplier가 getEmail만을 갖고 있어서 다른 부분들을 안쓰게 하면서 역할을 명확히 하려고?
어떤 내용에 대한 PR인가요?
회원가입 기능 구현했습니다.
변경 사항
변경된 부분에 대한 상세한 내용을 나열해주세요
무엇을 위주로 보면 좋을까요?
관련된 이슈
closes (#1)
테스트 방법
테스트 코드 추가하겠습니다!