Jonas Lundberg
Jonas Lundberg
This is a nice idea and feature for RESPX. I think it would be quite simple to support without too much effort. We already have the side effects to play...
Ping @StephenBrown2 😉 ...your old #16 are kind-of being re-visited...any thoughts?
Thoughts @sidharthv96 ?
Yes, I think that we should break this issue down into separate pull request, where the first one is responsible for the pass through callback hook enhancement. One alternative solution...
> If you can give some pointers, I can try to take a shot at enhancing the pass through behavior to make this work. If we go with `return PassThrough(...)`...
A note/fyi....when looking at how we mock and how to implement a pass through response hook, it will have to callback using the transport result, i.e. raw url, stream, etc......
> opening a draft pull-request would make it easier for people to pick up from where this was left. Agree, a draft would be good 😉
See you in the future @StephenBrown2
Yes, unfortunately this is true. Simply put, this is due to both the _ConnectionPool_ and the _Connection_ `httpcore` transports are patched by respx to ensure mocking is always happening regardless...
Great! I see three alternatives solving the over-counting issue related to using the `httpcore` _Mocker_: 1. Flag the request, like you're proposing, _but rather use that flag in the stats...