Skip to content

Make underlying http client also public when configured #287

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

Closed
wants to merge 1 commit into from

Conversation

ruudk
Copy link
Contributor

@ruudk ruudk commented Nov 19, 2018

Q A
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Related tickets follow up of #280
Documentation not needed
License MIT

What's in this PR?

This makes the underlying http client also public when configured.

Why?

Something I didn't add in #280 but need when using mocks. This is needed for #286.

Checklist

  • Updated CHANGELOG.md
  • Documentation: no need to update

For example: when configuring an `acme` client that is public, it should make `httplug.client.acme.client` also public.
@dbu
Copy link
Collaborator

dbu commented Dec 13, 2018

i closed #286 because i don't see the use case. similar here, i don't see the use in having this internal service be public. if you really need it to be public for a special test setup, i suggest that you add a compiler pass in your application that finds the corresponding services and changes them to public after this bundle has defined them as private.

@dbu dbu closed this Dec 13, 2018
@ruudk ruudk deleted the client-public branch December 13, 2018 14:52
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