Fix #374: Document WarpCore content accessors#586
Conversation
|
Warning Review limit reached
More reviews will be available in 51 minutes and 14 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 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 |
Release Preflight
If you tag this commit as |
|
@codex Code Lawyer Activity Summary
Validation:
|
What changed
Added block JSDoc to the
WarpCorecontent accessor declarations.Why
The content methods were the remaining inconsistent public-surface declarations from the bad-code report. This keeps the declaration surface aligned with the surrounding block-style documentation.
Closes #374
Validation
npm run typecheck:src -- --pretty falsenpx eslint src/domain/WarpCore.ts