-
-
Notifications
You must be signed in to change notification settings - Fork 289
feat(http-manager)!: default to configurable pooling connection manager #384
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
in SpotifyApi; if not called, default is BasicHttpClientConnectionManager
and eliminated setConnectionManager()
…lean and restored previous SpotifyApi.build() with no parameter
…oolingConnectionManager
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #384 +/- ##
============================================
+ Coverage 66.08% 66.09% +0.01%
- Complexity 661 664 +3
============================================
Files 183 184 +1
Lines 7103 7100 -3
Branches 1148 1145 -3
============================================
- Hits 4694 4693 -1
- Misses 1506 1507 +1
+ Partials 903 900 -3 ☔ View full report in Codecov by Sentry. |
|
Let's not get too worried about the patch's code coverage 😄 |
gahisee
left a comment
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.
looks fine to me.
|
Got nothing to add either, looks good! I will give the RC a full spin soonish. If I don't report back, assume everything is working fine :D |
|
Tested |
|
Thank you for the feedback! 🚀 |
Adds one commit to @gahisee's PR #375, which aligns the builder pattern so that it matches way it's used throughout this project: allowing the connection manager to be configurable. It also lets the connection manager default to a pooling connection manager so that most users don't face issue #383.
This is a breaking change (which is not an issue for me, those occur rarely) as the
connectTimeoutConnectionConfigcannot be set anymore as is. Instead, a (basic) connection manager having thatConnectionConfigwould need to be set now if it's needed to be kept.@gahisee @Selbi182 @linde9821 please tell me what you think, I'd release a release candidate for this.
@gahisee your pull request would be merged automatically as well when this one is merged as this PR builds on top of yours so all your stats will be kept. I just thought it's a good idea to have this PR open to see the proposed changes more clearly when comparing against
master💡