-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Use Json TypeInfoResolverChain #47450
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
35 changes: 14 additions & 21 deletions
35
src/Http/Http.Extensions/src/ProblemDetailsJsonOptionsSetup.cs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,33 +1,26 @@ | ||
// Licensed to the .NET Foundation under one or more agreements. | ||
// The .NET Foundation licenses this file to you under the MIT license. | ||
|
||
using System.Text.Json.Serialization.Metadata; | ||
using Microsoft.AspNetCore.Http.Json; | ||
using Microsoft.Extensions.Options; | ||
|
||
namespace Microsoft.AspNetCore.Http; | ||
|
||
internal sealed class ProblemDetailsJsonOptionsSetup : IPostConfigureOptions<JsonOptions> | ||
/// <summary> | ||
/// Adds the ProblemDetailsJsonContext to the current JsonSerializerOptions. | ||
/// | ||
/// This allows for consistent serialization behavior for ProblemDetails regardless if | ||
/// the default reflection-based serializer is used or not. And makes it trim/NativeAOT compatible. | ||
/// </summary> | ||
internal sealed class ProblemDetailsJsonOptionsSetup : IConfigureOptions<JsonOptions> | ||
{ | ||
public void PostConfigure(string? name, JsonOptions options) | ||
public void Configure(JsonOptions options) | ||
{ | ||
switch (options.SerializerOptions.TypeInfoResolver) | ||
{ | ||
case DefaultJsonTypeInfoResolver: | ||
// In this case, the current configuration is using a reflection-based resolver | ||
// and we are prepending our internal problem details context to be evaluated | ||
// first. | ||
options.SerializerOptions.TypeInfoResolver = JsonTypeInfoResolver.Combine(ProblemDetailsJsonContext.Default, options.SerializerOptions.TypeInfoResolver); | ||
break; | ||
case not null: | ||
// Combine the current resolver with our internal problem details context (adding last) | ||
options.SerializerOptions.AddContext<ProblemDetailsJsonContext>(); | ||
break; | ||
default: | ||
// Not adding our source gen context when TypeInfoResolver == null | ||
// since adding it will skip the reflection-based resolver and potentially | ||
// cause unexpected serialization problems | ||
break; | ||
} | ||
// Always insert the ProblemDetailsJsonContext to the beginning of the chain at the time | ||
// this Configure is invoked. This JsonTypeInfoResolver will be before the default reflection-based resolver, | ||
// and before any other resolvers currently added. | ||
// If apps need to customize ProblemDetails serialization, they can prepend a custom ProblemDetails resolver | ||
// to the chain in an IConfigureOptions<JsonOptions> registered after the call to AddProblemDetails(). | ||
options.SerializerOptions.TypeInfoResolverChain.Insert(0, new ProblemDetailsJsonContext()); | ||
} | ||
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.