Changed members API tests to avoid rewire#28654
Conversation
no ref Replaced module mutation in the members API unit test with an explicit dependency seam on the members API factory.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe Possibly related PRs
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx run-many -t test:unit -p ghost |
✅ Succeeded | 32s | View ↗ |
nx run-many -t lint -p ghost |
✅ Succeeded | 42s | View ↗ |
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗
☁️ Nx Cloud last updated this comment at 2026-06-17 14:37:20 UTC
no ref The rewire replacement should not expose every internal constructor as a second production argument. Moving the magic-link member resolution into a focused helper keeps the MembersAPI constructor unchanged while giving the gift redemption behavior a real test boundary.
no ref The de-rewire pass does not need a new magic-link helper or constructor seam here. Stubbing the existing class prototypes keeps the test on real module boundaries while leaving the MembersAPI implementation unchanged.

Summary
Tests