Implement an AppContext compatibility switch re-enabling reflection fallback in STJ source generators. #75694
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 #75615 to release/7.0-rc2.
Customer Impact
.NET 7 introduced an intentional breaking change which removes silent fallback to reflection-based serialization in System.Text.Json source generators. Based on early feedback we have been receiving from customers and partner teams, it appears that quite a few users have (mostly accidentally) taken a dependency on the fallback behavior (see dotnet/aspnetcore#43894, dotnet/aspnetcore#43236 for a few examples).
Even though a workaround for the breaking change has been documented, it still requires a code change which might not be possible in certain scenaria. This PR introduces an
AppContext
compatibility switch (namedSystem.Text.Json.Serialization.EnableSourceGenReflectionFallback
) that brings back the reflection fallback logic for source generators.Testing
Added unit tests validating behavior with the compatibility switch enabled.
Risk
Low. Makes minimal adaptations to product code that only kicks in when the switch is enabled.