-
Notifications
You must be signed in to change notification settings - Fork 4
refactor: use container-provided channel registry #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
||
@Inject | ||
DefaultGrpcChannelRegistry(GraphQlServiceLifecycle serviceLifecycle) { | ||
serviceLifecycle.shutdownCompletion().thenRun(this.delegate::shutdown); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No longer required, the channel registry is managed by the container.
Codecov Report
@@ Coverage Diff @@
## main #106 +/- ##
============================================
- Coverage 58.36% 58.18% -0.18%
Complexity 255 255
============================================
Files 87 87
Lines 1309 1313 +4
Branches 39 39
============================================
Hits 764 764
- Misses 515 519 +4
Partials 30 30
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. |
Description
Small refactor to use the container's channel registry rather than building our own internally