fix: fallback to direct README fetch when backend proxy fails#214
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughReadmeModal component refactoring centralizes README content and candidate fetching into reusable ChangesREADME Loading with Backend/GitHub Fallback
Sequence DiagramsequenceDiagram
participant Component as ReadmeModal
participant FetchHelper as fetchReadmeContentFromAvailableSource
participant Backend as backend adapter
participant GitHub as GitHubApiService
Component->>FetchHelper: fetch README
FetchHelper->>Backend: try backend proxy
Backend--XGitHub: on error
FetchHelper->>GitHub: fallback to direct API
GitHub->>FetchHelper: return content
FetchHelper->>Component: content or abort
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
Summary
Review / Audit Notes
""), preserving the existing no-README UX.src/components/ReadmeModal.tsxandsrc/components/ReadmeModal.test.tsxare included in the commit. Existing unrelated working-tree changes were left uncommitted.Tests
npx eslint src/components/ReadmeModal.tsx src/components/ReadmeModal.test.tsxnpm test -- ReadmeModal --runnpm test -- --runNote: full
npm run lintcurrently fails on unrelated working-tree changes inReleaseTimeline.tsxanduseAppStore.ts; README files pass targeted lint.🤖 Generated with Claude Code
Summary by CodeRabbit
Bug Fixes
Tests