You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are cases when it's required to extact$wrappedDriver
And which cases would that be? The middleware stacks are not designed to be unwrapped and that's kind of on purpose.
but AbstractDriverMiddleware does not have such public api.
Please be aware that AbstractDriverMiddleware is by no means a contract. It's a utility class. The contract of a driver middleware class is the Driver interface. A class that only implements that interface and not the abstract class is still a valid driver middleware class.
So, even if we did add such a method to AbstractDriverMiddleware, it would not guarantee that you could actually unwrap the whole driver stack.
I don't know what problem you are trying to solve, but I would kindly ask you to find a different way.
this could be a wrong implementation from auditor lib, but it's OCP, we decorate connection/driver to add extra functionality - so imo valid solution to check instance if needed, but because driver/connection could be wrapped by many other decorators logic could be broken, that's why need to rewind or unwrap.
Feature Request
There are cases when it's required to extact
$wrappedDriver
butAbstractDriverMiddleware
does not have such public api.DamienHarper/auditor#184
Summary
Adding get-method for
$wrappedDriver
The text was updated successfully, but these errors were encountered: