-
Notifications
You must be signed in to change notification settings - Fork 33
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
overrideStandardValueWriter
only applied to first java.nio.file.Path
valued field of bean
#112
Comments
@jhonnen That does sound like an interesting bug. Thank you for reporting! |
I wonder if this has something to do with the fact |
overrideStandardValueWriter
only applied to first field of beanoverrideStandardValueWriter
only applied to first java.nio.file.Path
valued field of bean
Yes, somehow detection as
|
…alizer Fix #112: make custom serialization work for `java.nio.file.Path`
Ok, looks like there is a problem that is generalizable for "simple" (recognized and supported JDK types) types like |
The
overrideStandardValueWriter
mechanism seems to work only for the first field of the given type for a Bean. Here's a failing test case that demonstrates the issue (can be added toValueWriterModifierTest
):The test fails with
--> on the second
Path
field, theIterable
serialization wrongly has precedence over my configured writer.The text was updated successfully, but these errors were encountered: