-
Notifications
You must be signed in to change notification settings - Fork 0
refactor(user,reservationn): 빈값 해결 #61
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
Merged
The head ref may contain hidden characters: "feature/#60-\uC608\uC57D\uB9AC\uD329\uD1A0\uB9C1"
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
socialType 필드 추가는 좋은 개선이지만, toEntity() 메서드와의 일관성 문제가 있습니다.
socialType 필드를 DTO에 추가한 것은 유연성을 높이는 좋은 개선사항입니다. 하지만 43번 줄의
toEntity()메서드에서는 여전히SocialType.LOCAL을 하드코딩하고 있어, 새로 추가된 필드 값이 실제로 사용되지 않고 있습니다.일관성을 위해 다음과 같이 수정해주세요:
public User toEntity() { return User.builder() .email(email) .password(password) .nickname(nickname) - .socialType(SocialType.LOCAL) + .socialType(SocialType.valueOf(socialType)) .role(Role.MANAGER) .build(); }또는 socialType 필드를 실제로 사용하지 않을 예정이라면, 필드를 제거하거나 용도를 명확히 해주시면 좋겠습니다.
📝 Committable suggestion
🤖 Prompt for AI Agents