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
Afterburner Interferes With Options Respecting Include.NON_NULL #226
Comments
Interesting. Does the order of registering the modules make a difference? |
Another thing that may be of importance here is that Jackson 2.6 has improved support for "referential" types, aimed at better support for @christophercurrie JDK8 module and Guava have relevant code, and maybe former is simpler example, on how to resolve option(al) type as |
I don't think that the Scala module has yet picked up on that. I'll dig into the JDK8 module's examples as time allows. |
Yes, registering Afterburner after the Scala module does not cause this issue. I am not sure whether it might cause issues with Afterburner, though. |
As a side-effect of the 2.7.4 release, the non-standard Thanks 👍 |
@omervk Thank you for verifying this. |
If Afterburner (
jackson-module-afterburner
) is registered on an ObjectMapper beforeDefaultScalaModule
, it interferes with (at least) howNone
is serialized whenInclude.NON_NULL
is in play.Expected:
Actual:
The text was updated successfully, but these errors were encountered: