-
Notifications
You must be signed in to change notification settings - Fork 30
Decouple from Pimple #50
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
Hi @bradjones1, thanks for forcing me to think about this. I'm thinking of changing the constructor as follows public function __construct(array $options[]) rather than public function __construct(Psr\Container\ContainerInterface $container) What do you think? Do you have any suggestions? |
@gnello I've made a fork removing pimple and switching from Guzzle to any PSR7/17/18 compatible http client implementation. If you are ok with this changes I'm willing to continue working on that in next several weeks until changes are merged to the upstream. |
both those changes sound great -- can you also update the documentation to use the Symfony HttpClient instead of guzzle? And if it's ready, submit a PR, since having guzzle and pimple just for this library seems a bit heavy. Thanks. |
Thanks for this handy package. Pimple development has ended/is in maintenance mode, and I don't necessarily think this package need be aware of the dependency injection container per se. Open to decoupling from
pimple/pimple
and refactoring to allow dependencies like the HTTP client be pulled in as a dependency from your DIC of choice?The text was updated successfully, but these errors were encountered: