test(rivetkit-core): cover sleep/destroy guards and prevent_sleep no-op#4750
test(rivetkit-core): cover sleep/destroy guards and prevent_sleep no-op#4750NathanFlurry merged 1 commit intomainfrom
Conversation
d844ecd to
e68bdc2
Compare
89647d5 to
ed93ef7
Compare
391fcaa to
e4395f8
Compare
e4395f8 to
d1c2bbf
Compare
ed93ef7 to
8d93174
Compare
Code ReviewPR: test(rivetkit-core): cover sleep/destroy guards and prevent_sleep no-op SummaryThis PR adds 6 targeted tests verifying documented invariants from the rivetkit-core CLAUDE.md. The coverage is well-chosen and the test structure is consistent with existing tests in the module. Strengths
Minor Issues1. Comment describes "what", not "why" In // The sleep predicate ignores prevent_sleep entirely.
assert_eq!(ctx.can_sleep().await, CanSleep::Yes);CLAUDE.md says to write comments only when the why is non-obvious, not to describe what the code does. The 2. Cross-guard scenarios not tested (optional follow-up)
Not Issues
VerdictClean, well-scoped test additions. The comment-style issue is minor and does not block merging. The cross-guard gap is a follow-up, not a blocker. |
Preview packages published to npmInstall with: npm install rivetkit@pr-4750All packages published as Engine binary is shipped via Docker images: docker pull rivetdev/engine:slim-8a663b7
docker pull rivetdev/engine:full-8a663b7Individual packagesnpm install rivetkit@pr-4750
npm install @rivetkit/react@pr-4750
npm install @rivetkit/rivetkit-napi@pr-4750
npm install @rivetkit/workflow-engine@pr-4750 |

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: