Skip to content

Make main aliases public #254

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

Merged
merged 1 commit into from
Feb 20, 2018
Merged

Make main aliases public #254

merged 1 commit into from
Feb 20, 2018

Conversation

stof
Copy link
Contributor

@stof stof commented Feb 20, 2018

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Related tickets n/a
Documentation n/a
License MIT

What's in this PR?

Symfony 3.4+ is making services private by default, so this requires configuring the visibility explicitly.

Why?

This allows keeping $this->get('httplug.client') working without deprecation.

For now, I haven't applied this change to the different client services, but it might make sense as well.

Symfony 3.4+ is making services private by default, so this requires configuring the visibility explicitly.
Copy link
Collaborator

@dbu dbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed! and thanks for the fix stof

@dbu dbu merged commit 1b1ced7 into php-http:master Feb 20, 2018
@stof stof deleted the patch-2 branch February 20, 2018 11:21
@stof
Copy link
Contributor Author

stof commented Feb 20, 2018

what about non-default clients ?

@dbu
Copy link
Collaborator

dbu commented Feb 20, 2018

the should be injected in DI. but i am not opposed to make the client services public.

@stof
Copy link
Contributor Author

stof commented Feb 20, 2018

well, if you consider that using DI for other clients is better, that's fine with me (I don't have a use case for that need anyway as I have only 1 client currently)

@dbu
Copy link
Collaborator

dbu commented Feb 20, 2018

i guess if you have multiple clients configured, you would want to inject them and not pull. if there is a use case for it, i am not opposed to a pull request however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants