(fix) : 멤버 정산내역 입금 요청 상태 노출#61
Conversation
|
Need the big picture first? Review this PR in Change Stack to see what changed before going file by file. 전체 요약경비 상세 조회 응답에서 매니저 권한 여부에 따라 결제요청 정보 노출을 제어하는 기능 변경. 응답 모델 시그니처 확장, 서비스 계층의 항상 조회 패턴, 테스트 검증 정렬이 포함. 변경사항경비 응답 모델 및 접근 제어 로직
예상 코드 리뷰 난이도🎯 2 (Simple) | ⏱️ ~12 분 관련 PR
시 한 수
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📝 테스트 커버리지 리포트입니다!
|
There was a problem hiding this comment.
🧹 Nitpick comments (1)
src/test/java/com/dnd/moddo/domain/memberExpense/service/QueryMemberExpenseServiceTest.java (1)
159-188: ⚡ Quick win비총무 시나리오는 컨트롤러 레벨 계약도 같이 고정해 두는 편이 좋겠습니다.
지금은 서비스 DTO까지만 검증해서, JSON 직렬화에서
paymentRequestId만 숨기고paymentRequestStatus/paymentRequestStatusLabel은 계속 내려줘야 하는 계약 회귀를 바로 잡기 어렵습니다.src/test/java/com/dnd/moddo/domain/memberExpense/controller/MemberExpenseControllerTest.java:53-63와 같은 위치에 비총무 케이스를 하나 추가해 두면 이번 변경 의도가 API 경계까지 고정됩니다.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/test/java/com/dnd/moddo/domain/memberExpense/service/QueryMemberExpenseServiceTest.java` around lines 159 - 188, Add a controller-level test to lock the API contract for non-manager flows: in MemberExpenseControllerTest create a test (mirror the service test findMemberExpenseDetailsBySettlementId_Success_WhenNotManager) that performs an HTTP call to the endpoint handled by the controller (use the same request params/groupId and a non-manager user) and asserts the JSON response hides paymentRequestId (absent or null) while still returning paymentRequestStatus and paymentRequestStatusLabel with expected values; this ensures the controller serialization/DTO mapping matches the service behavior and prevents regressions at the API boundary.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In
`@src/test/java/com/dnd/moddo/domain/memberExpense/service/QueryMemberExpenseServiceTest.java`:
- Around line 159-188: Add a controller-level test to lock the API contract for
non-manager flows: in MemberExpenseControllerTest create a test (mirror the
service test findMemberExpenseDetailsBySettlementId_Success_WhenNotManager) that
performs an HTTP call to the endpoint handled by the controller (use the same
request params/groupId and a non-manager user) and asserts the JSON response
hides paymentRequestId (absent or null) while still returning
paymentRequestStatus and paymentRequestStatusLabel with expected values; this
ensures the controller serialization/DTO mapping matches the service behavior
and prevents regressions at the API boundary.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 2393d776-8409-4b8e-ae9b-3e01cbdd4111
📒 Files selected for processing (3)
src/main/java/com/dnd/moddo/event/application/query/QueryMemberExpenseService.javasrc/main/java/com/dnd/moddo/event/presentation/response/MemberExpenseItemResponse.javasrc/test/java/com/dnd/moddo/domain/memberExpense/service/QueryMemberExpenseServiceTest.java
#️⃣연관된 이슈
X
🔀반영 브랜치
fix/payment-request-settlement-detail -> develop
🔧변경 사항
💬리뷰 요구사항(선택)
X
Summary by CodeRabbit
릴리스 노트