Fixed two cases of incorrect error reporting about DeserializationFeature#3038
Closed
jellevoost wants to merge 1 commit intoFasterXML:masterfrom
Closed
Fixed two cases of incorrect error reporting about DeserializationFeature#3038jellevoost wants to merge 1 commit intoFasterXML:masterfrom
jellevoost wants to merge 1 commit intoFasterXML:masterfrom
Conversation
cowtowncoder
added a commit
that referenced
this pull request
Feb 1, 2021
Member
|
@jellevoost Thank you! Since this is present in earlier versions too ( Thank you once again for contributing this fix. |
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
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.
While using the DeserializationFeature.FAIL_ON_NULL_CREATOR_PROPERTIES setting I came across an error that did not match with the actual setting it was referring about. This led to an error referring to 'FAIL_ON_NULL_FOR_CREATOR_PARAMETERS' which I found to not exist on the DeserializationFeature.
I would assume this setting was renamed at some point in the past and the report was not adjusted accordingly, but I could be wrong about that of course.
In case I'm missing something for this PR just let me know.