This repository was archived by the owner on Jul 2, 2023. It is now read-only.
Change the signature of the entity readers to take content type and class type. #25
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
budjb
force-pushed
the
jackson-entity
branch
3 times, most recently
from
ea9e15f to
6d83ba8
Compare
Contributor
|
Looks good to me! |
Contributor
|
Looking forward to this! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is in support of adding larger Jackson compatibility. It makes sense to make the readers aware of what they may be converting some entity into, and whether they can actually support the content type of that entity.
The changes contained here are a reflection of the conversation in #23.