-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAIL_ON_MISSING_EXTERNAL_TYPE_ID_PROPERTY setting ignored when creator properties are buffered #2404
Comments
…tor properties The feature was only getting examined in the "normal" case, and not when using creator properties Fixes FasterXML#2404
this may be the same issue reported in #1527, as we initially saw this working with kotlin classes. Attached PR fixes in our case and includes a test that demonstrates the issue with pure java classes. |
…tor properties The feature was only getting examined in the "normal" case, and not when using creator properties Fixes FasterXML#2404
…tor properties The feature was only getting examined in the "normal" case, and not when using creator properties Fixes FasterXML#2404
Looks legit: thank you for contribution! Quick question: have I asked for (and received) CLA yet? If not, it's at: https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf and the usual way is to print, fill & sign, scan, email to |
CLA emailed, thanks! |
#1341 added the ability to disable a FAIL_ON_MISSING_EXTERNAL_TYPE_ID_PROPERTY deserialization feature. However, it appears to only be observed through the
complete(JsonParser p, DeserializationContext ctxt, Object bean)
codepath, and is not examined in thecomplete(JsonParser p, DeserializationContext ctxt, PropertyValueBuffer buffer, PropertyBasedCreator creator)
variant that gets used with, for example, @JsonCreator annoations.It looks like adding the same check for
prop.isRequired() || ctxt.isEnabled(DeserializationFeature.FAIL_ON_EXTERNAL_TYPE_ID_MISSING_PROPERTY))
immediately before callingctxt.reportInputMismatch
should allow the feature to work properly in this case?Tested on jackson-databind 2.9.9
The text was updated successfully, but these errors were encountered: