feat: Override object mapper #287
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closing this and will create 2 prs, One for code and other for doc fixes. Due to docs build issue, code change can move forward. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
**Issue #275 and #66
Description of changes:
Ability to override default object mapper used for serialization while logging received event. This can also be used to control what is logged from event based on the configuration of object mapper. Refer PowerToolLogEventEnabledWithCustomMapper.java
Checklist
Breaking change checklist
RFC issue #:
Migration process documentedImplement warnings (if it can live side by side)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.