feat(notification): notification read API 구성 #28 - #66
Open
wlyoon921 wants to merge 2 commits into
Open
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
🚫 Excluded labels (none allowed) (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
wlyoon921
force-pushed
the
feat/28-notification-read-api
branch
from
July 30, 2026 11:50
98c15cd to
79483c2
Compare
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
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.
Summary
공지, QnA, 전형요강 조회 REST API와 JPA 조회 adapter를 구성했습니다.
명세 기준의 목록/상세 응답 DTO와 mapper를 추가했습니다.
notification adapter-in/out Bazel 의존성을 정리했습니다.
Related Issue
Related to #28
Scope
In scope:
Out of scope:
Implementation
다음 조회 API를 구현했습니다.
Controller는 NotificationPort를 호출하고 mapper를 통해 명세 응답으로 변환합니다.
조회 데이터는 JPA repository adapter를 통해 MySQL에서 가져오도록 구성했습니다.
Not found 상황은 NotificationNotFoundException을 통해 공통 error response로 변환합니다.
Testing
Deployment Notes
Feature flag: 없음
Migration required: 예, notification DB schema 필요
Rollout considerations:
Checklist