Conversation
…제를 해결 Changes: - ChatMessage.sender를 nullable로 변경하여 탈퇴한 사용자의 메시지 유지 - ChatMessageRepository에 nullifySenderByWorkspaceMemberId() 추가 - leaveWorkspace()와 kickMember()에서 멤버 삭제 전 sender null 처리 - ChatConverter에서 null sender를 "탈퇴한 사용자"로 표시
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
☝️Issue Number
close # 118
📌 개요
🐛 fix: WorkspaceMember 탈퇴/추방 시 외래 키 제약 조건 오류 수정
워크스페이스 멤버가 탈퇴하거나 추방될 때, ChatMessage 엔티티와의 외래 키 제약 조건으로 인해 삭제가 실패하는 버그 수정
🔁 변경 사항
sender 필드를 nullable = true로 변경
멤버 삭제 전에 해당 멤버가 보낸 모든 메시지의 sender를 null로 설정
클라이언트에서는 "탈퇴한 사용자"로 표시
📸 스크린샷
👀 기타 더 이야기해볼 점