Skip to content
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

Merged
merged 14 commits into from
Oct 1, 2023
Merged

[Feat]회원가입 기능 구현 #18

merged 14 commits into from
Oct 1, 2023

Conversation

kssumin
Copy link
Contributor

@kssumin kssumin commented Oct 1, 2023

어떤 내용에 대한 PR인가요?

회원가입 기능 구현했습니다.

변경 사항

변경된 부분에 대한 상세한 내용을 나열해주세요

  1. request -> entity를 변환하는 converter interface를 사용했습니다.

무엇을 위주로 보면 좋을까요?

관련된 이슈

closes (#1)

테스트 방법

테스트 코드 추가하겠습니다!

@kssumin kssumin self-assigned this Oct 1, 2023
@kssumin kssumin merged commit 7b4d9bb into weekly Oct 1, 2023
0 of 2 checks passed
@kssumin kssumin deleted the feat/#1/signup branch October 1, 2023 06:30
Copy link
Contributor

@jinwooseok jinwooseok left a comment

Choose a reason for hiding this comment

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

구우우욷

@PHS00
Copy link
Contributor

PHS00 commented Oct 4, 2023

마커 인터페이스를 사용하는 이유가 궁금합니다

Copy link
Contributor

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) {
Copy link
Contributor

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) {
Copy link
Contributor

Choose a reason for hiding this comment

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

supplier를 쓰는 이유? supplier가 getEmail만을 갖고 있어서 다른 부분들을 안쓰게 하면서 역할을 명확히 하려고?

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.

3 participants