fix: update class signature to adapt Jackson 2.18 changes in deserialization of data class#279
Open
mukul-tyagi wants to merge 1 commit intoePages-de:masterfrom
Conversation
…on of data classes
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
1 participant
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.
With Jackson 2.18.2, while deserializing the Schema class it gives below exception
Cannot construct instance of
com.epages.restdocs.apispec.model.Schema(although at least one Creator exists): cannot deserialize from Object value (no delegate- or property-based Creator)at [Source: UNKNOWN; line: 83, column: 7] (through reference chain: com.epages.restdocs.apispec.model.ResourceModel["response"]->com.epages.restdocs.apispec.model.ResponseModel["schema"])
and to resolve it Jackson library provided the workaround used in the MR changes
Related to ##278