Uh oh!
There was an error while loading. Please reload this page.
Fix default handling for value types when converter based on interface - #42319
Conversation
| } | ||
| [Fact] | ||
| public static void JsonIgnoreCondition_WhenWritingDefault_OnBoxedPrimitive() |
There was a problem hiding this comment.
This was passing before, just added the test.
| } | ||
| [Fact] | ||
| public static void JsonIgnoreCondition_WhenWritingDefault_OnRootTypes() |
There was a problem hiding this comment.
This was passing before, just added the test.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
steveharter
commented
Sep 17, 2020
Runtime failure in mono unrelated:
|
Fixes#42237
When a custom converter is based on an interface and a corresponding property is based on a value type that implements the interface, default handling was not working. This PR fixes that.
Some local benchmarks showed no regression for the happy path that doesn't hit this edge case.