Conversation
Collaborator
|
고생하셨습니달 |
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
2 participants
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.
✨ 관련 이슈
🔎 작업 내용
• POST /api/rooms 엔드포인트 추가
• 요청 DTO에 roomName, memo, startDate, endDate, memberIds 필드 정의
• X-MEMBER-ID 헤더로 요청 유저를 방장(ownerId)으로 설정
• 방 생성 시 Room 저장 후, 방장 + 초대 멤버를 RoomMember에 함께 저장되도록 로직 구현
📌 참고 사항
• 방 생성 시 Room + RoomMember를 한 번에 생성하는 트랜잭션 구조가 괜찮은지 확인 부탁드립니다.
• X-MEMBER-ID 헤더로 방장을 주입하는 방식이 팀 전체 인증/인가 전략과 맞는지 봐주시면 좋겠습니다.
• RoomResponse에 포함된 필드(특히 memberIds)가 프론트 요구사항에 충분한지/불필요한 필드는 없는지도 피드백 부탁드립니다.
📷 이미지 첨부
✅ Check List