Skip to content

[Deploy] develop → main 배포 반영 - #340

Merged
Seojegyeong merged 12 commits into
mainfrom
develop
Jul 28, 2026
Merged

[Deploy] develop → main 배포 반영#340
Seojegyeong merged 12 commits into
mainfrom
develop

Conversation

@Seojegyeong

@Seojegyeong Seojegyeong commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

🚨 관련 이슈

N/A

✨ 변경사항

  • 🐞 BugFix Something isn't working
  • 💻 CrossBrowsing Browser compatibility
  • 🌏 Deploy Deploy
  • 🎨 Design Markup & styling
  • 📃 Docs Documentation writing and editing (README.md, etc.)
  • ✨ Feature Feature
  • 🔨 Refactor Code refactoring
  • ⚙️ Setting Development environment setup
  • ✅ Test Test related (storybook, jest, etc.)

✏️ 작업 내용

N/A

😅 미완성 작업

N/A

📢 논의 사항 및 참고 사항

N/A

💬 리뷰어 가이드 (P-Rules)
P1: 필수 반영 (Critical) - 버그 가능성, 컨벤션 위반. 해결 전 머지 불가.
P2: 적극 권장 (Recommended) - 더 나은 대안 제시. 가급적 반영 권장.
P3: 제안 (Suggestion) - 아이디어 공유. 반영 여부는 드라이버 자율.
P4: 단순 확인/칭찬 (Nit) - 사소한 오타, 칭찬 등 피드백.

Summary by CodeRabbit

  • 새로운 기능

    • 설정 화면에서 워크스페이스별 알림 설정을 불러오고 관리할 수 있습니다.
    • 채널 및 워크스페이스 알림 변경 사항을 저장할 수 있습니다.
  • 버그 수정

    • 알림 설정을 불러오는 동안 저장 버튼이 비활성화됩니다.
    • 설정 조회에 실패하면 오류 안내와 재시도 버튼을 제공합니다.
    • 워크스페이스 변경 시 알림 설정 상태가 올바르게 동기화됩니다.

@Seojegyeong Seojegyeong self-assigned this Jul 28, 2026
@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

알림 설정 조회 API와 쿼리 훅을 추가하고, Setting 화면에 알림 설정 동기화·저장·로딩·오류·재시도 처리를 연동했습니다. 대시보드 일일 지표의 기본 날짜 범위도 갱신했습니다.

Changes

알림 설정 조회 및 설정 화면 연동

Layer / File(s) Summary
알림 설정 조회 계층
src/api/notification/notification.ts, src/lib/queryKeys.ts, src/hooks/setting/useMyNotificationSettings.ts
조직별 알림 설정 GET API와 notification.settings 쿼리 키를 추가하고, 조직이 선택된 경우에만 조회하는 훅을 구현했습니다.
설정 화면 알림 상태 연동
src/pages/setting/Setting.tsx
알림 설정을 draft/saved 상태에 동기화하고, 저장 조건·로딩 스켈레톤·오류 메시지·재시도 버튼·오류 토스트 중복 방지 로직을 추가했습니다.

대시보드 지표 기간

Layer / File(s) Summary
기본 지표 날짜 범위 갱신
src/constants/dashboard/overviewMetricsRange.ts
일일 지표 기본 startDate2026-06-15, endDate2026-07-15로 변경했습니다.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Setting
  participant useMyNotificationSettings
  participant NotificationAPI
  participant NotificationSection
  Setting->>useMyNotificationSettings: selectedOrgId 기반 조회
  useMyNotificationSettings->>NotificationAPI: GET 알림 설정 요청
  NotificationAPI-->>useMyNotificationSettings: 설정 데이터 또는 오류
  useMyNotificationSettings-->>Setting: 로딩·오류·재시도 상태 반환
  Setting->>NotificationSection: 알림 draft/saved 상태 렌더링
  Setting->>NotificationAPI: 오류 시 설정 재조회
Loading

Possibly related PRs

Suggested labels: 📬 API

Suggested reviewers: yermim, jjjsun

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed 배포 PR의 핵심 변경을 간결하게 담고 있어 제목이 변경사항과 잘 맞습니다.
Description check ✅ Passed 필수 섹션은 대부분 채워져 있고 Deploy 변경사항도 체크되어 있어 템플릿을 대체로 만족합니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

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.

@Seojegyeong
Seojegyeong requested review from YermIm and jjjsun July 28, 2026 12:34
@Seojegyeong Seojegyeong added the 🌏 Deploy 배포 관련 label Jul 28, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
src/hooks/setting/useMyNotificationSettings.ts (1)

1-1: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

상대 경로 대신 @/ 별칭을 사용해주세요.

이 경로는 파일 이동 시 깨지기 쉽고, 저장소의 import 규칙과도 다릅니다.

수정 예시
-import { useCoreQuery } from "../customQuery";
+import { useCoreQuery } from "`@/hooks/customQuery`";

As per coding guidelines, “Use @/ alias for all imports.”

🤖 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/hooks/setting/useMyNotificationSettings.ts` at line 1, Update the import
in useMyNotificationSettings to use the repository’s `@/` alias instead of the
relative ../customQuery path, while preserving the imported useCoreQuery symbol.

Source: Coding guidelines

🤖 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.

Inline comments:
In `@src/pages/setting/Setting.tsx`:
- Around line 219-239: Connect the notification save flow in Setting using
useCoreMutation from customQuery.ts to persist channel and workspace
notification changes through the server. Move setSavedChannel,
setSavedWorkspaceNotif, and the success-toast state behind the mutation’s
successful response, and derive savedAnyNotification only from changes confirmed
as persisted; preserve validation and selectedOrgId guards.
- Around line 291-306: Separate the notification settings initialization in the
useEffect from subsequent refetch handling: reset draftChannel and
draftWorkspaceNotif to server values only on the first successful response after
selectedOrgId changes, while preserving dirty drafts during later
notificationSettings updates. Keep savedChannel and savedWorkspaceNotif
synchronized with the latest server values, and ensure save completion updates
saved state without overwriting unsaved drafts.

---

Nitpick comments:
In `@src/hooks/setting/useMyNotificationSettings.ts`:
- Line 1: Update the import in useMyNotificationSettings to use the repository’s
`@/` alias instead of the relative ../customQuery path, while preserving the
imported useCoreQuery symbol.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 144cee73-5537-466a-84c0-cb5e11e28ca0

📥 Commits

Reviewing files that changed from the base of the PR and between af341d9 and 2754209.

⛔ Files ignored due to path filters (5)
  • tests/ai-analysis.spec.ts is excluded by none and included by none
  • tests/fixtures/auth.ts is excluded by none and included by none
  • tests/login.spec.ts is excluded by none and included by none
  • tests/navigation.spec.ts is excluded by none and included by none
  • tsconfig.node.json is excluded by none and included by none
📒 Files selected for processing (5)
  • src/api/notification/notification.ts
  • src/constants/dashboard/overviewMetricsRange.ts
  • src/hooks/setting/useMyNotificationSettings.ts
  • src/lib/queryKeys.ts
  • src/pages/setting/Setting.tsx

Comment thread src/pages/setting/Setting.tsx
Comment thread src/pages/setting/Setting.tsx
@Seojegyeong
Seojegyeong merged commit 2e27b56 into main Jul 28, 2026
3 checks passed
Seojegyeong added a commit that referenced this pull request Jul 29, 2026
[Deploy] develop → main 배포 반영- #340
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🌏 Deploy 배포 관련

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants