Skip to content

feat: 일정 그리드 요일 헤더에 실제 날짜(M/D) 표시 (#123) - #124

Merged
Siul49 merged 1 commit into
devfrom
fix/116-day-headers-dates
Jul 10, 2026
Merged

feat: 일정 그리드 요일 헤더에 실제 날짜(M/D) 표시 (#123)#124
Siul49 merged 1 commit into
devfrom
fix/116-day-headers-dates

Conversation

@Siul49

@Siul49 Siul49 commented Jul 10, 2026

Copy link
Copy Markdown
Owner

🚀 작업 내용 (What)

  • 초대 링크/일정 조율 현황 화면의 요일 헤더에 실제 날짜(M/D)를 함께 표시
  • 슬롯 라벨·히트맵 요일 헤더에도 동일 formatDayWithDate 적용
  • CodeRabbit 피드백 반영: 잘못된 dayCode 방어, ICS 100KB 제한을 isIcs에만 적용
  • 최신 dev 기준으로 feat: 요일 헤더에 자동 날짜 표시 추가 #116 stale 브랜치를 재구현

📣 핵심 변경 이유 (Why)

  • 요일만 있으면 어느 날짜인지 알기 어려움
  • 기존 #116은 dev 대비 크게 뒤처져 conflict/리뷰 지적 상태였음

📸 스크린샷 (Visuals, 선택)

  • 로컬 단위 검증: lint-staged(eslint/prettier) 통과

⚠️ 체크리스트 (Checklist)

  • 브랜치 컨벤션(feature/00-name)을 지켰나요?
  • 커밋 컨벤션(feat:, fix: 등)을 지켰나요?
  • 작업 전에 관련 이슈를 생성하고 연결했나요?
  • 내 코드가 팀의 기존 코드를 망가뜨리지 않았는지 확인했나요?

🔗 관련 이슈 (Issue)

Close #123

Supersedes #116

formatDayWithDate로 초대/결과 화면 요일 라벨에 날짜를 붙이고,
잘못된 dayCode를 방어하며 ICS 100KB 제한을 isIcs에만 적용한다.
@vercel

vercel Bot commented Jul 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
moim-app Ready Ready Preview, Comment Jul 10, 2026 6:44am

@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Siul49, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 14bc4c3f-1fcf-4e41-ad93-6e32916612cb

📥 Commits

Reviewing files that changed from the base of the PR and between 4c1dde5 and 510cd28.

📒 Files selected for processing (1)
  • src/app/schedule/[id]/ScheduleRoomClient.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/116-day-headers-dates

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.

@Siul49
Siul49 merged commit 8dd87d8 into dev Jul 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT] 일정 그리드 요일 헤더에 실제 날짜(M/D) 표시

1 participant