-
Notifications
You must be signed in to change notification settings - Fork 116
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
Optional
deserialization, serialization ignore contentConverter
#294
Labels
2.17
has-failing-test
Indicates that there exists a test case (under `failing/`) to reproduce the issue
Milestone
Comments
Thank you for reporting this @richardsonwk -- it definitely sounds like bug and is not intentional. |
cowtowncoder
added
the
has-failing-test
Indicates that there exists a test case (under `failing/`) to reproduce the issue
label
Dec 18, 2023
cowtowncoder
changed the title
Optional serialization ignores contentConverter but not contentUsing
Jan 24, 2024
Optional
deserialization, serialization ignore contentConverter
cowtowncoder
added a commit
that referenced
this issue
Jan 24, 2024
Closed
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2.17
has-failing-test
Indicates that there exists a test case (under `failing/`) to reproduce the issue
I was surprised to find that
contentConverter
does not work withOptional
, butcontentUsing
does. I think this is effectively the same as #97.The output is
A slight tweak to instead specify a content serializer fixes it:
The output is then
This is not a difficult workaround, so it's no problem - just unexpected.
The text was updated successfully, but these errors were encountered: