test(start): cover prerender crawl request and output boundaries - #8338
test(start): cover prerender crawl request and output boundaries#8338Sheraff wants to merge 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
View your CI Pipeline Execution ↗ for commit 48468ac
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview2 package(s) bumped directly, 2 bumped as dependents. 🟩 Patch bumps
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe React Start example adds a crawl-boundary splat route, enables crawl-specific prerender settings, registers the route in generated types, and adds an end-to-end build test with Nx integration and documentation. ChangesPrerender crawl boundary
Sequence Diagram(s)sequenceDiagram
participant BuildTest as prerender-crawl.test.ts
participant Build as Vite build
participant CrawlRoute as crawl-boundaries.$ route
participant Output as generated HTML output
BuildTest->>Build: run crawl build with test environment
Build->>CrawlRoute: request /crawl-boundaries/seed
CrawlRoute-->>Build: return crawl-boundary links
Build->>Output: write prerendered HTML
BuildTest->>Output: verify links and output boundaries
Merge Risk: ⚪ Minimal · up to This adds isolated prerender-crawl coverage for the React Start example without release behavior changes. The generated output and external-link boundaries are validated, so the change is mergeable with normal checks. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 5 files. (2 skipped: 2 unsupported.)
✨ Finishing Touches 💡 1📝 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 |
🎯 Changes
Add a real prerender-build regression test for crawl-discovered traversal and protocol-relative links, including encoded protocol-relative input. A fixture page supplies these links alongside a normal link. The test verifies that normal crawling works, a separate local HTTP server receives no requests, and every generated HTML file stays inside the client output directory.
The cases share one build and HTTP listener. The test uses the public build command and file-route handlers, with temporary output and listener cleanup. Changes are limited to the e2e fixture, its generated route tree, and tests.
Validation: the new build test passes with application TypeScript checks; changed source/test files pass ESLint, and all 21 existing prerender unit tests pass.
✅ Checklist
🚀 Release Impact
Summary by CodeRabbit
New Features
Tests
Documentation