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

GH-2611: Remove MimeTypeJsonDeserializer #3097

Merged
merged 1 commit into from
Mar 4, 2024

Conversation

Wzy19930507
Copy link
Contributor

Closes #2611

@artembilan artembilan merged commit 265e55f into spring-projects:main Mar 4, 2024
3 checks passed
@artembilan
Copy link
Member

@Wzy19930507 ,

Thank you for contribution as always!

Please, take a look what I did with commit message: 265e55f.

Technically you can do exactly the same when you open PR in your commit message.
It becomes a PR description and then when we merge, there is no need in extra modifications from our side.
The Fixes: # pattern would trigger automatic issue closing and so on for other actions if we need to back-port it or so.

@Wzy19930507
Copy link
Contributor Author

No thanks, Spring kafka is a great framework that let me easy and security to work with kafka and spring. I‘m happy to contirbution ​on it.

Thanks for your guidance, I have learned and do it next PR.

@Wzy19930507 Wzy19930507 deleted the GH-2611 branch March 4, 2024 16:07
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.

Calling DefaultKafkaHeaderMapper constructor with the same ObjectMapper instance may result memory leak
2 participants