-
Notifications
You must be signed in to change notification settings - Fork 388
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
Propagate client's adapter to API categories #939
Conversation
Hi @WilkenSteiner ! Thanks for this submission, I will have to take some time to go over it in a little more detail. While the original designers are not active here anymore, off the top of my head, I would say that it was probably expected that the adapter would not b re-assigned after So I am inclined to agree that this is more intuitive, but let me think about it a bit and discuss with the other maintainers. Also huge thanks for adding a regression test! |
@WilkenSteiner by the way, I've just created a poll and discussion topic about the Adapter system, and I'd appreciate a vote and/or some feedback if you have a few moments: |
@briantist Thank you for considering and putting a more structural spin on it! I left a comment in the poll with my use case. |
@WilkenSteiner |
Codecov Report
@@ Coverage Diff @@
## develop #939 +/- ##
===========================================
+ Coverage 81.34% 81.64% +0.30%
===========================================
Files 65 65
Lines 2969 3002 +33
===========================================
+ Hits 2415 2451 +36
+ Misses 554 551 -3
|
Propagate the adapter used by the client to all handlers registered on the client.
Previously, setting the adapter (and thus session/connection pool) on the client after initialization would only replace the adapter owned by the client, leaving the adapters of all API categories untouched.
Notes