chore: 기사님 상세 SSR prefetch 오류 진단 추가 - #104
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughSSR 상세 데이터 프리패치 오류를 표준 문자열로 변환합니다. 오류를 ChangesSSR 상세 프리패치 오류 처리
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
6 tasks
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.
📋 작업 내용
기사님 상세 페이지의 서버 prefetch 실패 원인을 브라우저 콘솔에서 확인할 수 있도록 임시 진단 로그를 추가했습니다.
🔥 변경 사항
MoverDetailPageMoverDetailView✅ 체크리스트
💬 To Reviewer
배포 환경에서 SSR 상세 prefetch가 실패해
initialDetail이null로 렌더링되는 현상을 확인하기 위한 임시 진단 코드입니다.배포 후 브라우저 콘솔에서 오류 원인을 확인한 뒤, 원인 해결 PR에서 해당
console.error와 오류 전달 Prop은 제거할 예정입니다.