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.
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
3단계 - 즐겨찾기 기능 구현 #355
base: hscom96
Are you sure you want to change the base?
3단계 - 즐겨찾기 기능 구현 #355
Changes from 27 commits
b199287
7730e74
bf6f801
0ebcbd6
ea1eca3
dcb9838
8109ffa
73ba170
3d45966
9570e2b
4aa8fb1
6ed9daf
18e19c0
797aff7
1859e9b
6b73538
b794805
91d8c97
05305bc
2d746dd
0c419ad
a8d4b2a
fefa7ed
d9c8b9b
49171fe
d1b97b5
33bc833
e194e54
0e880a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
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.
UserDetail 인터페이스를 제거하고 User 클래스로 대체하기 보다
User 클래스가 UserDetail 인터페이스를 구현하는 형태는 어떨까요?
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.
네 먼저 말씀하신대로 다음 PR과 같이 구현 해봤는데 0e880a2
말씀하신 부분에서 궁금한점이 있습니다.
인터페이스 (ex. UserDetail) 사용의 효과중 하나로 의존성 역전을 위한것으로 이해했는데
제가 만든 프로젝트에서는 member 패키지에서 LoginMember가 삭제되고, User객체는 auth 패키지에만 있어서
기존처럼 User클래스가 UserDetail 인터페이스를 상속 안해줘도 member에서 auth패키지로 의존성이 한방향으로만 흐르고 있고
또한 User와 UserDetail이 같은 패키지 내부에 있는데
여기서 User가 UserDetail을 구현하는 장점이 어떤게 있을지 알 수 있을까요? 🤔