[release/9.0-preview5] Fix STJ support for System.Reflection.NullabilityInfoContext.IsSupported = false #102876
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.
Backport of #102852 to release/9.0-preview5
/cc @eiriktsarpalis
Customer Impact
.NET 9 Preview 5 added support for nullable reference types in System.Text.Json via #102499. The reflection-based serializer uses the
System.Reflection.NullabilityInfoContext
class to derive this metadata. What this change didn't anticipate is thatNullabilityInfoContext
can be disabled via a feature flag, and Blazor wasm disables that feature flag by default. This results in an exception being thrown every time Blazor wasm attempts to useJsonSerializer
using the reflection-based serializer.This PR adds checking for the
NullabilityInfoContext
feature flag so that the serializer can handle applications where the flag has been turned off.Regression
Yes
Testing
Added unit testing covering the impacted scenario.
Risk
Low.