Default JsonSerializerIsReflectionEnabledByDefault to true on Blazor WASM. #31909
Conversation
dotnet-issue-labeler
bot
added
Area-AspNetCore
|
Thanks for your PR, @eerhardt. |
src/BlazorWasmSdk/Targets/Microsoft.NET.Sdk.BlazorWebAssembly.Current.targets
Outdated
Show resolved
Hide resolved
| @@ -17,6 +17,9 @@ Copyright (c) .NET Foundation. All rights reserved. | |||
| <!-- Trimmer defaults that depend on user-definable settings. | |||
| This must be configured before it's initialized in the .NET SDK targets (which are imported by the Razor SDK). --> | |||
| <SuppressTrimAnalysisWarnings Condition="'$(SuppressTrimAnalysisWarnings)' == '' And '$(TrimmerDefaultAction)' != 'link'">true</SuppressTrimAnalysisWarnings> | |||
|
|
|||
| <!-- Similarly these feature switches must be configured before they are initialized in imported SDKs --> | |||
| <JsonSerializerIsReflectionEnabledByDefault Condition="'$(JsonSerializerIsReflectionEnabledByDefault)' == ''">true</JsonSerializerIsReflectionEnabledByDefault> | |||
There was a problem hiding this comment.
Does this need any testing?
There was a problem hiding this comment.
See the note in the top comment.
NOTE: I don't know how to test this at this layer. If anyone has a good recommendation for how to test it, I am open to suggestions.
There was a problem hiding this comment.
AFAIK blazor apps don't run here. So best way to test it is to locally run blazor app with the built SDK.
There was a problem hiding this comment.
This can't be disabled for blazor apps, if the user disables this, we should emit an error instead in the context of blazor webassembly apps or simply ignore the user choice.
The framework is dependent on this feature for basic functionality (JS interop)
Since #31626, the Web SDK is defaulting
JsonSerializerIsReflectionEnabledByDefault=falsewhenever PublishTrimmed or PublishAot is set totrue. However, this also affects Blazor WASM since it is importing the Web SDK. For Blazor WASM, we need to keep the normal default ofJsonSerializerIsReflectionEnabledByDefault=true, so it doesn't break existing Blazor WASM apps that are relying on JsonSerializer using Reflection.See discussion in dotnet/runtime#84378.
NOTE: I don't know how to test this at this layer. If anyone has a good recommendation for how to test it, I am open to suggestions.