-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Missing null
writes when writing Object[]
values
#10
Comments
More likely related to #116 (?): looks like nulls for "array in array" are suppressed. This could be somewhat problematic even for other entries since "null value" would not get written. |
null
writes when writing Object[]
valuesnull
writes when writing Object[]
values
@cowtowncoder Hey, Is anyone working on this I would be happy to pick it up Added a gist for the current behaviour in 2.9.0 and what I think the desired behaviour should be https://gist.github.com/daliclass/19507eb79939e6ad716b30cd241c612b |
@cowtowncoder Is there any workaround for the issue? |
@ganchurin not aware of work-arounds unfortunately. If anyone has time to look into this, I would be happy to help validate fix, integrate, but right now I do not have time in short term. I will add this as something to (re-)evaluate tho as it is an important issue. |
Workaround: |
Work around FasterXML/jackson-dataformats-text#10. Signed-off-by: Pierre-Alexandre Meyer <[email protected]>
Work around FasterXML/jackson-dataformats-text#10. Signed-off-by: Pierre-Alexandre Meyer <[email protected]>
This also affects writing By the way: Thank you very much for developing/providing Jackson. |
null
writes when writing Object[]
valuesnull
writes when writing Object[]
values
Added reproduction as failing test, hoping to look into the issue next. |
(moved from FasterXML/jackson-dataformat-csv#116 by @georgewfraser)
When writing arrays to CSV, if there is a null, columns get written out of order. Reproduced in 2.7.1 with this test: https://gist.github.com/georgewfraser/164647fbaca61aadf9ee :
The text was updated successfully, but these errors were encountered: