Skip to content
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

Make ZipkinHttpClientSender the default BytesMessageSender #43085

Closed

Conversation

wickdynex
Copy link
Contributor

@wickdynex wickdynex commented Nov 10, 2024

Description

This PR switch the @Import order, and switch the order of HttpClientSenderConfiguration.class and UrlConnectionSenderConfiguration.class, also adjust the declaration order in file ZipkinConfigurations.javaAnd in order to pass the ZipkinConfigurationsSenderConfigurationTests.java, I try to adapt the filter order and test method name.


Related Issue

Fixed #42589


Type of Change

  • Refactor feature
  • Modify related tests
  • Documentation update

Checklist

  • I have reviewed the code for any potential issues or improvements.
  • I have run tests locally and they are passing.
  • I have followed the coding style and conventions of the project.

Screenshots

image

Additional Notes

I switch the @Import order to make ZipkinHttpClientSender to be the default BytesMessageSender implement🥳, also adapt test file ZipkinConfigurationsSenderConfigurationTests to be passed which is mentioned in #42589 (comment). And if this PR is ready to merge, could u plz assign #43047, #43048 to me🥺, I'll be glad to do so. If there's anything need to be done, plz comment🥰. Btw, this PR need to be merged to 3.5.x branch, but this branch doesn't exist, so plz create a new one as soon as possible🤩.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Nov 10, 2024
@philwebb philwebb added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Nov 12, 2024
@philwebb philwebb added this to the 3.5.x milestone Nov 12, 2024
@philwebb philwebb changed the title Refactor/Make ZipkinHttpClientSender the default BytesMessageSender Make ZipkinHttpClientSender the default BytesMessageSender #42589 Jan 13, 2025
@philwebb philwebb changed the title Make ZipkinHttpClientSender the default BytesMessageSender #42589 Make ZipkinHttpClientSender the default BytesMessageSender Jan 13, 2025
@philwebb philwebb self-assigned this Jan 13, 2025
philwebb pushed a commit that referenced this pull request Jan 13, 2025
Switch `HttpClientSenderConfiguration` and `UrlConnectionSenderConfiguration`
import order to set default sender.

See gh-43085
@philwebb philwebb closed this in 1c991a7 Jan 13, 2025
@philwebb philwebb modified the milestones: 3.5.x, 3.5.0-M1 Jan 13, 2025
@philwebb
Copy link
Member

Thanks @wickdynex!

@wickdynex
Copy link
Contributor Author

Thanks @wickdynex!

🤗Welcome, it's happy to work with you all.

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

Successfully merging this pull request may close these issues.

Make ZipkinHttpClientSender the default BytesMessageSender
3 participants