refactor(trogon-nats): align JetStream trait signatures with async_nats#73
Conversation
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryMedium Risk Overview Updates the real client, mocks, and Written by Cursor Bugbot for commit a0c4254. This will update automatically on new commits. Configure here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughThis PR generalizes NATS JetStream trait method signatures to accept flexible input types instead of concrete ones. The Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 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 |
Code Coverage SummaryDetailsDiff against mainResults for commit: a0c4254 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Summary
JetStreamContext::get_or_create_streamnow takesS: Into<stream::Config> + Sendinstead of concretestream::Config, matching async_natsJetStreamPublisher::js_publish_with_headersnow takesS: ToSubject + Sendinstead ofString, matching async_natsJetStreamConsumerFactory::create_consumerleft unchanged — it composes two async_nats calls (get_stream + create_consumer) which is an intentional abstraction