Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Ensure JsonSerializerOptions always returns a JsonTypeInfo for object. #87093

Merged

Conversation

eiriktsarpalis
Copy link
Member

Fix #87073.

@ghost
Copy link

ghost commented Jun 3, 2023

Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis
See info in area-owners.md if you want to be subscribed.

Issue Details

Fix #87073.

Author: eiriktsarpalis
Assignees: -
Labels:

area-System.Text.Json

Milestone: -

@eiriktsarpalis eiriktsarpalis merged commit fe98008 into dotnet:main Jun 5, 2023
@eiriktsarpalis eiriktsarpalis deleted the always-return-obj-typeinfo branch June 5, 2023 13:21
eerhardt added a commit to dotnet/aspnetcore that referenced this pull request Jun 7, 2023
dotnet-maestro bot added a commit to dotnet/aspnetcore that referenced this pull request Jun 8, 2023
[main] Update dependencies from dotnet/efcore dotnet/runtime


 - Fix Http Results test to respond to dotnet/runtime#87093

 - Convert to new generic JsonStringEnumConverter<TEnum> to fix JSON source generator warning.

InteractionType is used in a JsonSerializerContext. With dotnet/runtime#87224, there is now a warning to convert source generated usages of JsonStringEnumConverter to JsonStringEnumConverter<TEnum>.

I went ahead and updated the other 2 usages as well, to make them consistent.

 - Skip AcceptAsync_NoCertificateCallback_RemovedFromPendingConnections

See #48678
@ghost ghost locked as resolved and limited conversation to collaborators Jul 5, 2023
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using JsonTypeInfo<object> with JsonSerializerContext configured throws error during serialization steps
3 participants