-
Notifications
You must be signed in to change notification settings - Fork 39
Virtual packages #55
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
Comments
i think psr-client-implementation and methods-... are enough. not sure how much sense it makes to combine the two concepts and have one library consume the unified interface. or we could only have client-implementation and provide two classes in the utils repo that are client-implementation that can be set up with either type of client to add the other part. then you would always use a client that can do both concepts. |
The HttpClient exception only exists to ease type-hinting when both the interfaces are needed. I also think that the two are enough for dependency handling. |
Is it |
👍 we mainly need to adjust the existing adapters and the doc for this, right? |
Yes. |
|
[WIP] Remove discovery dependency
Currently we have adapter-implementation virtual package which could be renamed to client-implementation, however we now have three interfaces.
Possible virtual packages:
The text was updated successfully, but these errors were encountered: