docs(study): 7주차 React 입문 추가, 9주차 렌더링 진화로 개편#18
Conversation
- week7: 바닐라 JS 한계 → React 등장 이유 → 컴포넌트 → Virtual DOM 섹션 추가, Next.js 간략 소개로 마무리 - week9: 웹 보안 → CSR/SSR/SSG/ISR/PPR 렌더링 진화 + Web Vitals 측정으로 전면 개편 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Walkthrough두 주차 학습 콘텐츠 파일이 완전히 재작성되었습니다. week7은 React 기초 개념부터 프로젝트 구조 책임 분리와 도구 생태계까지 포괄하는 React 입문 강의로 구성되었고, week9는 웹 보안 주제에서 CSR/SSR/SSG/ISR/Streaming/PPR 렌더링 전략 진화와 Web Vitals 성능 측정으로 전환되었습니다. ChangesWeek 7: React 입문과 프로젝트 구조
Week 9: Next.js 렌더링 전략과 Web Vitals
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
seojing | eebd90d | Commit Preview URL Branch Preview URL |
May 11 2026, 05:43 AM |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
apps/web/content/study/clab-26-1/in-person/week7.mdx (1)
1-711:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win이 파일도 Prettier 경고를 해소해 주세요.
CI 로그 기준으로
Prettier --check경고가 발생했습니다. 문서 PR에서는 포맷 통일이 특히 중요하니prettier --write적용 후 재검증 부탁드립니다.🤖 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 `@apps/web/content/study/clab-26-1/in-person/week7.mdx` around lines 1 - 711, Prettier reported formatting issues in the MDX (week7.mdx); run prettier --write on the file and commit the changes to resolve the CI warning, ensuring the YAML frontmatter, JSX-like MDX components (Subtitle, Paragraph, Anchor), code blocks (```js/tsx/json), and inline braces/quotes/whitespace are normalized (no trailing spaces, consistent indentation, single/double quote style per project Prettier config), then re-run prettier --check; fix any remaining violations reported by Prettier for symbols like the top-level frontmatter (---), Subtitle/Paragraph/Anchor components, and fenced code blocks so the file passes CI.apps/web/content/study/clab-26-1/in-person/week9.mdx (1)
1-400:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winPrettier 경고를 먼저 정리해주세요.
CI에서 이 파일의
Prettier --check경고가 보고되었습니다. 문서 내용이 맞더라도 포맷 경고가 남아 있으면 이후 변경 검증이 어려워집니다.prettier --write로 파일 포맷을 정리한 뒤 다시 커밋해 주세요.🤖 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 `@apps/web/content/study/clab-26-1/in-person/week9.mdx` around lines 1 - 400, CI reported Prettier formatting warnings for the MDX content (the frontmatter and JSX blocks such as the title "프론트엔드 스터디 대면 9주차: Next.js 렌더링 진화와 웹 퍼포먼스" and components like <Subtitle>, <Paragraph>, <Anchor>), so run the project's formatter (prettier --write) on this MDX file to fix spacing, code-fence and JSX formatting, verify with prettier --check, then stage and recommit the formatted file so CI no longer reports Prettier errors.
🤖 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 `@apps/web/content/study/clab-26-1/in-person/week7.mdx`:
- Around line 705-707: The Anchor element linking to
"/blog/study/clab-26-1/week7" has an incorrect label ("불변성, 프로토타입, 타입 체크");
update the Anchor's inner text to match the current week 7 topic (e.g., "React
입문/프로젝트 구조") so the link label reflects the current curriculum; locate the
Anchor element in apps/web/content/study/clab-26-1/in-person/week7.mdx and
replace the displayed text between the opening and closing Anchor tags
accordingly.
---
Outside diff comments:
In `@apps/web/content/study/clab-26-1/in-person/week7.mdx`:
- Around line 1-711: Prettier reported formatting issues in the MDX (week7.mdx);
run prettier --write on the file and commit the changes to resolve the CI
warning, ensuring the YAML frontmatter, JSX-like MDX components (Subtitle,
Paragraph, Anchor), code blocks (```js/tsx/json), and inline
braces/quotes/whitespace are normalized (no trailing spaces, consistent
indentation, single/double quote style per project Prettier config), then re-run
prettier --check; fix any remaining violations reported by Prettier for symbols
like the top-level frontmatter (---), Subtitle/Paragraph/Anchor components, and
fenced code blocks so the file passes CI.
In `@apps/web/content/study/clab-26-1/in-person/week9.mdx`:
- Around line 1-400: CI reported Prettier formatting warnings for the MDX
content (the frontmatter and JSX blocks such as the title "프론트엔드 스터디 대면 9주차:
Next.js 렌더링 진화와 웹 퍼포먼스" and components like <Subtitle>, <Paragraph>, <Anchor>),
so run the project's formatter (prettier --write) on this MDX file to fix
spacing, code-fence and JSX formatting, verify with prettier --check, then stage
and recommit the formatted file so CI no longer reports Prettier errors.
🪄 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
Run ID: 579a56fe-b420-4c13-89b6-676c90ca5db5
📒 Files selected for processing (2)
apps/web/content/study/clab-26-1/in-person/week7.mdxapps/web/content/study/clab-26-1/in-person/week9.mdx
| - <Anchor href="/blog/study/clab-26-1/week7"> | ||
| 이번 주 학습 자료(week7) — 불변성, 프로토타입, 타입 체크 | ||
| </Anchor> |
There was a problem hiding this comment.
관련 포스팅 설명 문구가 현재 주차 주제와 어긋납니다.
/blog/study/clab-26-1/week7 링크 라벨이 "불변성, 프로토타입, 타입 체크"로 되어 있는데, 이번 파일의 7주차 주제(React 입문/프로젝트 구조)와 불일치해 보입니다. 링크 설명 문구를 현재 커리큘럼 기준으로 맞춰주세요.
🤖 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 `@apps/web/content/study/clab-26-1/in-person/week7.mdx` around lines 705 - 707,
The Anchor element linking to "/blog/study/clab-26-1/week7" has an incorrect
label ("불변성, 프로토타입, 타입 체크"); update the Anchor's inner text to match the current
week 7 topic (e.g., "React 입문/프로젝트 구조") so the link label reflects the current
curriculum; locate the Anchor element in
apps/web/content/study/clab-26-1/in-person/week7.mdx and replace the displayed
text between the opening and closing Anchor tags accordingly.
Summary
Changes
week7.mdx: React 기초(컴포넌트, Virtual DOM) 섹션 4개 추가, 제목/태그/설명 업데이트week9.mdx: 웹 보안 → Next.js 렌더링 진화 + 퍼포먼스 측정으로 전면 재작성🤖 Generated with Claude Code
Summary by CodeRabbit