test(9087): class toString reports source identity after #9465 - #9477
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe regression test now expects class references to stringify to their TypeScript source identity during dynamic ChangesClass Reference Stringification
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change updates stale test expectations to match the existing class stringification behavior and does not alter production code; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description explains the stale expectation, lists the affected behavior, records Node.js verification, and provides the local test command and result. It does not use all template headings or include the checklist, but it contains the critical change and verification details. ✨ 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 |
cargo-test-perry (2/8)fails onmain:The code is right; the test expectation is stale.
e86a2611cf("class name/toString/inspect report source identity", from #9465) deliberately changedString(SomeClass)fromfunction K() { [native code] }to the class's source text — which is what node does:issue_9087_class_ref_add.rswas not updated alongside it. This updates the three affected lines to the new (more spec-correct) output, with the node verification recorded inline so the next reader does not have to re-derive it.Perry reports the TypeScript source it compiled, so the
: numberannotation is retained in the expected string — that difference is noted in the comment.Verified locally:
cargo test -p perry --test issue_9087_class_ref_add→1 passed; 0 failed.Blocking:
cargo-test-perryis infull-suite-gate's needs, so this stops any release cut.Summary by CodeRabbit
valueOfcases.