Conversation
|
View your CI Pipeline Execution ↗ for commit c8bcf22
☁️ Nx Cloud last updated this comment at |
|
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; 8 remain after this review. 📝 WalkthroughWalkthroughThe autofix workflow now builds ChangesAutofix documentation generation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The documentation workflow should generate and commit only the intended reference documentation updates. No merge-blocking risk remains. 🚥 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 1 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 |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
size-limit report 📦
|
…eDoc conversion errors
🎯 Changes
Runs
pnpm run generate-docsinautofix.ci, next to the existingpnpm run format, so regenerated reference docs are committed back to the PR automatically. Two supporting fixes make that safe.Reference docs under
docs/framework/*/referenceare generated from source by TypeDoc, but nothing keeps them in sync: the script runs in no workflow andCONTRIBUTING.mddoes not mention it. Drift accumulated twice in two days:None of the causing PRs touched JSDoc. #11512 was a four-line bug fix in
utils.ts; that was enough to shift every symbol below it and breakDefined in:links on 28 pages across all seven frameworks. An author fixing a bug has no signal that reference docs need regenerating, so this cannot reasonably be caught by review or a checklist item.generate-docsnow builds the project it referencesangular-query-experimentalreaches@tanstack/query-devtoolsthrough a TypeScript project reference, so it consumes that package's emitted.d.tsrather than its source — the source is solid-js JSX and cannot be compiled under Angular's tsconfig. It is the only one of the seven documented packages with areferencesentry; the rest resolve entirely fromsrc.dist-tsis gitignored, so it is absent on a fresh clone and in CI, and TypeDoc then reportsTS6305and converts nothing. Rather than adding a build step to the workflow,generate-docsnow builds it itself:That keeps local runs and CI identical —
pnpm run generate-docsworks on a fresh clone with no extra step to remember.Failing loudly instead of emptying the output
generatePackageReferenceDocsemptiesoutputDirbefore conversion, then guards the rest withif (project). A failed conversion therefore left the directory empty and exited 0 — indistinguishable from "every page was intentionally deleted".The first push on this branch demonstrated it: the run went green and autofix committed the deletion of all 203 Angular pages. The script now throws instead, so CI stops rather than committing a destructive result. The follow-up push proved the fix end to end — autofix regenerated and restored all 203 pages, and
docs/is now identical tomain.Verified locally by deleting
packages/query-devtools/dist-ts:pnpm run generate-docsrebuilds it, reports noTS6305, and leavesdocs/unchanged.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit