Skip to content

fix: FAQ 저장 시 작성자(Member) 매핑 누락 수정 (#175)#186

Merged
Developer-Choi-Jae-Young merged 1 commit into
prography:mainfrom
Developer-Choi-Jae-Young:fix/175-faq-save-member-mapping
Jul 21, 2026
Merged

fix: FAQ 저장 시 작성자(Member) 매핑 누락 수정 (#175)#186
Developer-Choi-Jae-Young merged 1 commit into
prography:mainfrom
Developer-Choi-Jae-Young:fix/175-faq-save-member-mapping

Conversation

@Developer-Choi-Jae-Young

Copy link
Copy Markdown
Collaborator

PR 타입(하나 이상의 PR 타입을 선택해주세요)

  • Feat : 새로운 백엔드 기능 추가
  • Bug : 서버/로직 버그 발견 및 수정
  • Refactor : 백엔드 코드 구조 개선
  • Chore : 의존성/설정/인프라 유지보수
  • API : API 엔드포인트 및 스펙 변경
  • DB : DB 스키마/쿼리/마이그레이션 변경
  • Performance : 성능 개선 및 병목 최적화
  • Test : 백엔드 테스트 코드 추가/수정
  • Docs : 백엔드 문서 수정
  • Security : 보안 취약점 대응 및 강화

변경 사항

어드민(BO) 등에서 FAQ를 등록(저장)할 때, FAQ 엔티티와 작성자(Member) 연관관계가 바인딩되지 않은 상태로 저장되어 발생하던 누락 버그를 수정했습니다.

* `FaqServiceImpl.java`의 `saveFaq` 메서드 내에서 FAQ 빌더 패턴 호출 시 `.member(member)` 메서드를 연동하여 작성자 정보를 올바르게 바인딩했습니다.

테스트 결과

* FAQ 등록 API 호출 시 DB 상에 `member_id` 정보가 매칭되어 정상 저장되며, 관련 FAQ 서비스 유닛 테스트(`FaqServiceImplTest`)도 정상적으로 성공(BUILD SUCCESSFUL)함을 검증했습니다.

관련 이슈

* Closes #175

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Developer-Choi-Jae-Young, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 283d0d57-2fd8-4d23-ad37-86cffbd57a90

📥 Commits

Reviewing files that changed from the base of the PR and between 80aacc9 and 34c593a.

📒 Files selected for processing (1)
  • src/main/java/org/example/knockin/service/impl/FaqServiceImpl.java
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the 🐛 bug 서버/로직 버그 수정 (Backend bug fix) label Jul 20, 2026

@yourjinKR yourjinKR left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생하셨습니다.

@Developer-Choi-Jae-Young
Developer-Choi-Jae-Young merged commit ca7ffe6 into prography:main Jul 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🐛 bug 서버/로직 버그 수정 (Backend bug fix)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FAQ 저장 시 작성자(member) 매핑 누락

2 participants