Feature/37 - 게시글 수정/삭제 API 구현 #42
Merged
Conversation
This file contains 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
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🚀 개요
게시글 수정/삭제 API 구현
🔍 변경사항
⏳ 작업 내용
📝 논의사항
수정/삭제 시, 대상 게시글의 작성자와 현재 로그인 해 있는 사용자가 동일한지 확인하는 로직을 구현하고자 하는데, 하나의 User가 여러 트리하우스에 가입해 Member를 여러개 가진 경우, 이를 어떻게 처리해야할까요? 지난번 끔찍했던 코드(getTreeProfile)가 발생한 원인이 이곳입니다.