[REFACTOR]/#88- Member 엔티티의 필드를 변경하여 id와 userName으로 관리하기 #90
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.
🚀 개요
기존의 String 타입의 id로 Member를 관리하던 방식에서(인스타그램 느낌)
DB에 저장할 Long 타입의 고유 id 값 + String 타입의 고유 userName값으로 분리하는 작업을 진행했습니다.
🔍 변경사항
⏳ 작업 내용
📝 논의사항
Spring Security와 JWT 토큰 관련해서 memberId가 Long 타입으로 바뀐 것이 문제를 일으키진 않을지 궁금합니다!
(우선은 createAccessToken이나 toMemberSecurity에는 String.valueOf와 Long.valueOf을 이용해 넘겨주도록 수정했습니다.)