Document how to override ObjectMapper when using JDBI3#76
Merged
jhaber merged 2 commits intoHubSpot:masterfrom May 25, 2022
Merged
Document how to override ObjectMapper when using JDBI3#76jhaber merged 2 commits intoHubSpot:masterfrom
jhaber merged 2 commits intoHubSpot:masterfrom
Conversation
Member
|
Sorry for the delay and thanks for the PR! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I'm using JDBI3 with Rosetta and I had trouble figuring out how to override the default
ObjectMapper. There were only instructions for how to do this for JDBI2 but not JDBI3, so I figure adding this to advanced features could save folks some time.