Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough관리자 API의 사용자 권한 조회 요청 소스를 요청 본문( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 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. 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.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In
`@src/main/java/com/permitseoul/permitserver/domain/admin/base/api/controller/AdminController.java`:
- Around line 46-48: The query-param change removed DTO validation in
AdminController, so restore equivalent validation: annotate the controller
(AdminController) with `@Validated` (from
org.springframework.validation.annotation) and annotate the method parameter
(the String email in the getUserAuthority endpoint) with the javax/jakarta
validation constraints such as `@Email` and `@NotBlank` (i.e., use
`@RequestParam`("email") `@Email` `@NotBlank` final String email) and add the
necessary imports; this ensures request validation is performed when
adminService.getUserAuthority(email) is called.
🔥Pull requests
⛳️ 작업한 브랜치
👷 작업한 내용
admin 유저 정보 조회 req dto 변경
🚨 참고 사항