-
Notifications
You must be signed in to change notification settings - Fork 0
Fix#397: 페이지 리뉴얼을 위한 middleware 추가 #399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Caution Review failedThe pull request is closed. WalkthroughIntroduces a Next.js middleware to gate traffic via a maintenance mode flag, adds a static maintenance page, and removes a previously auto-rendered global overlay from the app bootstrap. Requests are redirected to /maintenance during maintenance mode; otherwise, normal routing proceeds. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant U as User
participant B as Browser
participant MW as Next.js Middleware
participant APP as Next.js App Router/Pages
participant M as /maintenance Page
U->>B: Navigate to any route
B->>MW: HTTP request
alt MAINTENANCE_MODE === "true"
alt Request path !== "/maintenance"
MW-->>B: Redirect to /maintenance (302)
B->>MW: GET /maintenance
MW-->>APP: Next()
APP-->>M: Render MaintenancePage
M-->>B: HTML
else Request path === "/maintenance"
MW-->>APP: Next()
APP-->>M: Render MaintenancePage
M-->>B: HTML
end
else Maintenance mode off
MW-->>APP: Next()
APP-->>B: Render requested page
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested labels
Suggested reviewers
Poem
✨ Finishing touches
🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal). Please share your feedback with us on this Discord post. 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 |
📝 추가 및 변경된 파일총 3개 파일 변경
|
📚 Storybook이 Chromatic에 배포되었습니다!
|
✅ Linked Issue
Summary by CodeRabbit
New Features
Chores