Skip to content

Public API cleanup, round 3 #783

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
Mar 27, 2020
Merged

Conversation

bording
Copy link
Collaborator

@bording bording commented Mar 26, 2020

Proposed Changes

Here is what I'm expecting to be the final public API cleanup PR for the 6.x release. This internalizes the ConsumerWorkService class.

After looking at it a bit, it turned out to not be as involved as I was initially thinking it would be.

As mentioned before, I don't think is the final thing to do to clean up the public API surface. We should take a hard look the RabbitMQ.Client namespace, where most of the public types live now.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

@lukebakken lukebakken self-assigned this Mar 27, 2020
@lukebakken lukebakken added this to the 6.0.0 milestone Mar 27, 2020
@lukebakken lukebakken merged commit 4a1d99b into master Mar 27, 2020
@lukebakken lukebakken deleted the internalize-consumer-work-service branch March 27, 2020 01:23
@lukebakken
Copy link
Collaborator

As mentioned before, I don't think is the final thing to do to clean up the public API surface. We should take a hard look the RabbitMQ.Client namespace, where most of the public types live now

I get the feeling like you'd like to see this for 6.0, correct?

@bording
Copy link
Collaborator Author

bording commented Mar 27, 2020

I get the feeling like you'd like to see this for 6.0, correct?

Ideally, yes, but I'm not sure it's something I can take on by myself in the timeframe you're talking about for 6.0.

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