-
Notifications
You must be signed in to change notification settings - Fork 624
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
@UseSerializers doesn't distinguish between nullable and non-nullable property when choosing KSerializer #984
Labels
Comments
shanshin
added a commit
to JetBrains/kotlin
that referenced
this issue
Nov 6, 2020
shanshin
added a commit
to JetBrains/kotlin
that referenced
this issue
Nov 11, 2020
This was referenced Nov 11, 2020
shanshin
added a commit
to JetBrains/kotlin
that referenced
this issue
Nov 24, 2020
Forgot to say: thanks for fixing this @shanshin! Was able to clean up a whole bunch of code :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If you have a nullable serializer for a type and a non-nullable serializer for a type and you want to register both of them with
@UseSerializers
, the nullable one is not chosen for nullable properties.To Reproduce
master...edenman:nullable-and-nonnullable-serializer
Expected behavior
Choose the correct serializer, either by checking the SerialDescriptor or introspecting the type argument on the KSerializer class.
Environment
The text was updated successfully, but these errors were encountered: