-
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
[YS-70] feat: JWT 토큰에 사용자 권한(RoleType) 정보 포함 #18
Conversation
Quality Gate passedIssues Measures |
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.
저희 비즈니스 로직이 유저 role에 따라 나누어진다는 점에서, @PreAuthroize 를 채택하고 이를 위해서 토큰 발급 시에 RoleType을 명시해주기 위한 사전 작업을 위한 PR이 잘 반영된 것 같아 approve 입니다 👍
특히 기존에 memberId가 아니라 member 로 파라미터를 받아오도록 리팩토링하신 점이 좋았어요.!! 수고하셨습니다~
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.
memberId가 아닌 member 파라미터 값을 조정하신 점이 좋았습니다 !
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.
네이밍 관련해서 MemberJpaRepository
와 MemberRepository
의 차이점에 대해 여쭈어봤는데, 구현하신 의도가 JPA와의 의존성에 대한 명시를 해주시겠다는 점을 말씀하셨습니다.
이에 통일성을 부여하기 위해서 MemberRpeository
로 컨벤션을 통일하기로 논의하였고, 이를 잘 반영해주신 것 같습니다 👍👍
* refact: delete unused file * refact: add roleName to Enum * feat: add memberRole to jwt token * test: add role validation test code * test: move usecase's test code to application package * style: delete unused import * refact: refactor exception handling to be more granular for token validation * style: rename JpaMemberRepository to MemberRepository for better clarity
💡 작업 내용
✅ 셀프 체크리스트
🙋🏻 확인해주세요
🔗 Jira 티켓
https://yappsocks.atlassian.net/browse/YS-70